Project Pro/Server connectivity works over http but not https

[Dave Farquhar]

Hello all,

I am hoping that someone knowledgeable will be able to help me, as I've
been staring at this problem for more than a week and at this point I
don't know where else to turn.

I have a Project Server set up with Project Server 2003, SQL Analysis
Services, IIS, and Sharepoint running on one box, with SQL Server 2000
running on a second box. Everything works fine over plain old HTTP on
port 80. I can connect with Project Pro or Project Web Access, and
everything works as expected.

Project Web Access works fine on HTTPS on port 443. Project Pro,
however, is unable to connect over HTTPS. When I look at the IIS logs
after an unsuccessful attempt with Project Pro, I find the following:

#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query
s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus
sc-win32-status
2006-10-02 16:53:43 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 443 - [ip of
client]Microsoft+Project+Workgroup+Message+Sender 200 0 64
2006-10-02 16:56:19 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 443 - [ip of client]
Microsoft+Project+Workgroup+Message+Sender 200 0 64
2006-10-02 17:03:43 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 443 - [ip of client]
Microsoft+Project+Workgroup+Message+Sender 200 0 64

Here's what a successful connection looks like:

2006-10-02 20:35:29 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 80 - [ip of client]
Microsoft+Project+Workgroup+Message+Sender 200 0 0
2006-10-02 20:35:29 W3SVC1 [ip of server] GET
/projectserver/Styles/1033/MSPROJECT.CSS - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0
2006-10-02 20:35:29 W3SVC1 [ip of server] GET
/projectserver/Styles/1033/PCSTYLES.CSS - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0
2006-10-02 20:35:30 W3SVC1 [ip of server] GET
/projectserver/Styles/1033/TBLMAIN.CSS - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0
2006-10-02 20:35:30 W3SVC1 [ip of server] GET
/projectserver/lgnpspj.asp - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0

I checked the permissions of pjdbcomm.dll and the isapi directory in
IIS Manager but didn't find anything that looked out of the
ordinary-anonymous connections allowed, and integrated Windows
authentication for authenticated access (which, I take, is moot if
anonymous connections are allowed?). When I connect up to the Project
Server with a browser and navigate to /projectserver/isapi/pjdbcomm.dll
the log indicates an sc-win32-status of 0, which tells me the browser
is hitting the file OK, although of course it doesn't display anything
useful. The lack of errors suggests IIS probably is configured OK.

Supposedly the sc-win32-status of 64 means "network name no longer
available," which suggests network connectivity errors. But the result
is consistent-it always works on port 80, never on 443. Same computers,
same network.

Does anyone have any ideas what I can try to get connectivity with
Project Pro working over https? If there's any more information that
would be helpful, please let me know and I'll gather it.

Thanks for any help you can provide.

 

[Michael]

I've not been able to get this to work either.

I'm seeing something similar, but what I see is an attempt to authenticate
by MS Project client via NTLM. Looking at Project Server's security event
logs should show this for you too I'm guessing. Per the event log online
lookup, code 64 means bad id or password. I found squirled awau in the
Microsoft Project Server Config Guide, that MS Project 2003 required direct
access to SQL Server of Project Server. If that's right, then using MS
Project over Internet/Extranet to get to Project Server is a non starter.
Someone else in a possibly related Extranet thread here mentioned that one
had to add MSADC virtual directory to ISA/IIS which I've not tried. It blows
me away from the MS Project Enteprise Options accounts UI for that MS
Project needs anything more than HTTP/HTTPS.

Have you tried setting MS Project's security config to mixed or Project
server authentication only? My thinking was that if Project Server
authentication was not set then NTLM/Kerbebos would be used over Internet.
But for me, nothing improved.

Hopefully someone can tell us how to expose Project Server 2003 to MS
Project 2003 client over Extranet,
Michael

Hello all,

I am hoping that someone knowledgeable will be able to help me, as I've
been staring at this problem for more than a week and at this point I
don't know where else to turn.

I have a Project Server set up with Project Server 2003, SQL Analysis
Services, IIS, and Sharepoint running on one box, with SQL Server 2000
running on a second box. Everything works fine over plain old HTTP on
port 80. I can connect with Project Pro or Project Web Access, and
everything works as expected.

Project Web Access works fine on HTTPS on port 443. Project Pro,
however, is unable to connect over HTTPS. When I look at the IIS logs
after an unsuccessful attempt with Project Pro, I find the following:

#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query
s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus
sc-win32-status
2006-10-02 16:53:43 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 443 - [ip of
client]Microsoft+Project+Workgroup+Message+Sender 200 0 64
2006-10-02 16:56:19 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 443 - [ip of client]
Microsoft+Project+Workgroup+Message+Sender 200 0 64
2006-10-02 17:03:43 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 443 - [ip of client]
Microsoft+Project+Workgroup+Message+Sender 200 0 64

Here's what a successful connection looks like:

2006-10-02 20:35:29 W3SVC1 [ip of server] POST
/projectserver/isapi/pjdbcomm.dll - 80 - [ip of client]
Microsoft+Project+Workgroup+Message+Sender 200 0 0
2006-10-02 20:35:29 W3SVC1 [ip of server] GET
/projectserver/Styles/1033/MSPROJECT.CSS - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0
2006-10-02 20:35:29 W3SVC1 [ip of server] GET
/projectserver/Styles/1033/PCSTYLES.CSS - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0
2006-10-02 20:35:30 W3SVC1 [ip of server] GET
/projectserver/Styles/1033/TBLMAIN.CSS - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0
2006-10-02 20:35:30 W3SVC1 [ip of server] GET
/projectserver/lgnpspj.asp - 80 - [ip of client]
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
200 0 0

I checked the permissions of pjdbcomm.dll and the isapi directory in
IIS Manager but didn't find anything that looked out of the
ordinary-anonymous connections allowed, and integrated Windows
authentication for authenticated access (which, I take, is moot if
anonymous connections are allowed?). When I connect up to the Project
Server with a browser and navigate to /projectserver/isapi/pjdbcomm.dll
the log indicates an sc-win32-status of 0, which tells me the browser
is hitting the file OK, although of course it doesn't display anything
useful. The lack of errors suggests IIS probably is configured OK.

Supposedly the sc-win32-status of 64 means "network name no longer
available," which suggests network connectivity errors. But the result
is consistent-it always works on port 80, never on 443. Same computers,
same network.

Does anyone have any ideas what I can try to get connectivity with
Project Pro working over https? If there's any more information that
would be helpful, please let me know and I'll gather it.

Thanks for any help you can provide.