Project Server connectivity to Project Pro works over http but not https?

D

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.
 
M

Mike Glen

Hi Dave,

Try posting on the server newsgroup. Please see FAQ Item: 24. Project
Newsgroups. FAQs, companion products and other useful Project information
can be seen at this web address: http://project.mvps.org/faqs.htm

Mike Glen
Project MVP


Dave said:
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.
Click to expand...
 
R

Roy_O

Hey Glen,
Instead of talking about shutting down this group why not just do it.
I'd end my subscription to this group except that more gets posted here
than the Project Server 2003 group which is where I assume you're
steering people.

Additionally most of these articles never get reposted. I suspect there
are lots more server questions out there, but people are simply giving
up in frustration.

Regards,
Roy

Mike said:
Hi Dave,

Try posting on the server newsgroup. Please see FAQ Item: 24. Project
Newsgroups. FAQs, companion products and other useful Project information
can be seen at this web address: http://project.mvps.org/faqs.htm

Mike Glen
Project MVP


Dave said:
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.
Click to expand...
Click to expand...
 
M

Mike Glen

Good point Roy, and I share your frustration! But it is for Microsoft to
actully pull the plug and we've been waiting now a few years for them to do
so. Unfortunately, the more people continue to post here the less likely
they are to close down! However, traffic is gradually waning as people read
the previous posts and get the message. The server newsgroup received 4228
postings to pro_and_server's 173 since July this year.

Mike Glen
Project MVP

Roy_O said:
Hey Glen,
Instead of talking about shutting down this group why not just do it.
I'd end my subscription to this group except that more gets posted
here than the Project Server 2003 group which is where I assume
you're steering people.

Additionally most of these articles never get reposted. I suspect
there are lots more server questions out there, but people are simply
giving up in frustration.

Regards,
Roy

Mike said:
Hi Dave,

Try posting on the server newsgroup. Please see FAQ Item: 24.
Project Newsgroups. FAQs, companion products and other useful
Project information can be seen at this web address:
http://project.mvps.org/faqs.htm

Mike Glen
Project MVP


Dave said:
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.
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Project Pro/Server connectivity works over http but not https 1
POST /projectserver/isapi/pjdbcomm.dll 4
"Action cannot be performed" in OWA 1
Project Professional/PWA login failures 2
PDS and SOAP 2
404 error on Project Workspaces 0
PWA errors after failed SP2a install 1
PWA down after attempted rollback after SP2a install failure 2

Top