Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
Playbooks error

Вопрос Playbooks error

  • Friday, May 04, 2012 9:20 PM
     
     
    Sign In to Vote
    0

     

    Hello,

    I'm having the a problem with connecting Playbook to PWA instance. In my case I have two PWA instances running in the same server, let's say:
     
    1. http://server/pwa
     
    2. http://server:1979/pwa
     
    Both running just fine.
     
    Running playbooks from the server I can connect to instance 1 but not to instance 2 I got the error "Invalid PWA instance, username and/or password"
     
    Any idea on why playbooks does not connect to the second instance, is it because the port?

    The second instance was created by using a full attach PS 2007 dbs, but again, the instance runs just fine
     
    Thanks for any help

    Daniel Villacis

     

All Replies

  • Friday, May 04, 2012 11:06 PM
     
     
    Sign In to Vote
    0

    Hello Daniel,

     Possibly yes, because port number 1979 is Unisql-java port.

    Try changing the port of the web application from IIS and update the AAM URL of the web application

    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn

     
  • Friday, May 04, 2012 11:23 PM
     
     
    Sign In to Vote
    0

    I tried to reproduce the issue, but unable to do so.

    I am able to connect to PWA site with port 1979.

    Try trurning off firewall on server and client system from where you are using Playbook

    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn

     
  • Saturday, May 05, 2012 12:44 AM
     
     
    Sign In to Vote
    0

    I'm running Playbooks directly from the server, so no problems with firewall.

    Maybe is because the second instance was created using ps 2007 dbs? Did you reproduce this scenario as well?

    Thanks!!

    Daniel Villacis

     
  • Saturday, May 05, 2012 4:44 AM
     
     
    Sign In to Vote
    0

    yes, I am able to connect using upgraded 2007 PWA databases using same port.

    check your DNS seeting for the second URL

    For a quick test, by updating AAM setting with the help of hosts file

    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn