SYMPTOMS
You receive the following error message when you run Microsoft
Content Management Server (MCMS) Site Deployment to import or export by using either a Site Deployment
script or Site Deployment Manager:
Error: 0
Description: The remote server returned an error: (403) Forbidden. Severity: 5
Source: System Debug info: N/A Extra info: N/A Client Source:
CExProgress::ProcessPackage Recommended Action: N/A
To receive this error message, you must use a SQL login to connect to the database, not a
trusted connection.
RESOLUTION
A 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, we recommend that you wait for the next Content Management Server 2002 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:
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 file attributes) 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
-----------------------------------------------------------------
03-Mar-2004 20:13 5.0.0.2524 2,232,416 Nrdcapplication.exe
03-Mar-2004 20:11 5.0.2524.0 2,060,800 Nrsitedeployserver.dll
Because you must use SQL logging, one method to work around this problem is to use a trusted connection. To do this, run the Database
Configuration Application (DCA). When you choose the computer that is running Microsoft SQL Server, and you choose the database
for MCMS, choose to enable a trusted connection. Make sure that the user who runs the
DCA has user rights to the MCMS database.