Article ID: 331971 - Last Review: February 1, 2007 - Revision: 3.7 SharePoint Team Services admin operation in Microsoft Project Web Access does not workThis article was previously published under Q331971 On This PageSYMPTOMSWhen you have performed the steps that are outlined in the
following Microsoft Knowledge base articles 819643
(http://support.microsoft.com/kb/819643/
)
PSVR2002: Port Error Message: Cannot Connect to the Specified Web Server Running SharePoint Team Services
818846
(http://support.microsoft.com/kb/818846/
)
PSVR2002: Connect Error, Cannot Connect to or Create the Specified Web Server Running SharePoint Team Services Error Messages
810604
(http://support.microsoft.com/kb/810604/
)
PSVR2002: How to Troubleshoot SharePoint Team Services
you can continue to receive one of the following
error messages:Microsoft Project Server cannot read from
the specified SharePoint database. The reasons could be:
Microsoft Project Server cannot connect to
the specified Web server running SharePoint Team services. The reasons could
be:
VBscript:Microsoft Project
Web Access Error occurred when creating subweb. Subweb does not seem to
exist. Cannot create subweb when the
Microsoft Project Server machine has Internet Explorer version 5.5 installed.
WORKAROUNDYou may be able to work around this problem by installing
Microsoft Internet Explorer 6.0 or later. RESOLUTIONService Pack InformationThis problem is corrected in Microsoft Project Server 2002 Service Pack 1.To resolve this problem, obtain the latest service pack for Project Server 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 867830
(http://support.microsoft.com/kb/867830/
)
How to obtain the latest Microsoft Project Server 2002 service pack Hotfix InformationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name -------------------------------------------------------------- 01-Oct-2002 04:50 3,525,120 Prjsvr10.msp 30-Aug-2002 00:13 611 Build.inc 05-Sep-2002 19:19 6,133 Clntutil.asp 05-Sep-2002 19:19 13,525 Dlmain.asp 05-Sep-2002 19:19 6,946 Issshell.asp 05-Sep-2002 19:19 16,837 Linkissu.asp 05-Sep-2002 19:19 3,975 New4task.asp 17-Sep-2002 00:56 10.2002.0.916 626,688 Pds.dll 24-Sep-2002 04:44 10.0.2002.923 909,824 Pj10od10.dll 29-Aug-2002 19:20 914,153 Pjclient.cab 01-Oct-2002 01:00 10.0.2002.930 167,936 Pjobjprv.dll 17-Sep-2002 01:12 10.0.2002.916 4,108,800 Pjoledb.dll 06-Aug-2002 18:16 3,584 Prjsvre.mst 05-Sep-2002 19:19 53,683 Svrdbdl.asp 818876
(http://support.microsoft.com/kb/818876/
)
PSVR2002: Setup Error "SharePoint Has Not Been Configured Properly for Project Server"
STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Project Server 2002 Service Pack 1. | Article Translations
|

Back to the top
