| Message ID | Severity | Message |
|---|---|---|
|
3500 |
Error |
The sender cannot connect to remote site %1 over the LAN. Possible cause: Remote site server %2 might not be connected to the LAN. Solution: Verify that site server %2 is connected to the LAN and functioning properly. Possible cause: Share %3 might not be accessible. Solution: Verify that share %3 is visible and that the address connection account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network. |
|
3501 |
Error |
The sender cannot connect to site %1 over RAS. Possible cause: Remote site server %2 might be down. Solution: Verify that remote site server %2 is connected to the network and functioning properly. Possible cause: Remote site server %2 might not be running RAS Server Service. Solution: Verify that remote site server %2 is running RAS Server Service. Possible cause: The phone book entry %3 in the default phone book might not contain the correct information. Solution: Verify that the phone book entry %3 contains valid information. Possible cause: Share %4 might not be accessible. Solution: Verify that share %4 is visible and that the address connection account has the necessary permissions to access the share. For a detailed explanation of the RAS error code, see the Windows NT documentation. |
|
3502 |
Error |
The address to site %1 is invalid. Possible cause: The destination site server name is missing. Solution: Define a valid address in the SMS Administrator console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses. |
|
3503 |
Error |
The address to site %1 is invalid. Possible cause: The destination share name is missing. Solution: Define a valid address in the SMS Administrator console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses. |
|
3504 |
Error |
The sender cannot install secondary site %1 on server %2. Possible cause: The targeted installation directory %3 does not reside on an NTFS partition. Solution: Select an NTFS partition for the installation directory or convert the current partition to NTFS. |
|
3505 |
Error |
The sender cannot install secondary site %1 on server %2 because the sender cannot create the SMS Bootstrap initialization file %3. Possible cause: The SMS Service account for site %1 might not have the appropriate privileges to create the initialization file Solution: Verify that the account has Administrator privileges to server %2. Possible cause: There is not enough free disk space on server %2. Solution: Make more space available on the destination drive. |
|
3506 |
Error |
The sender cannot install secondary site %1 on server %2 because it cannot retrieve the encryption public key. Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
3507 |
Error |
The sender cannot install secondary site %1 on server %2 because it cannot query the status of the SMS Bootstrap service on server %2. Possible cause: The SMS Service account for site %1 might not have the appropriate privileges to server %2. Solution: Make sure the Service account has Administrator privileges to server %2. |
|
3508 |
Error |
The sender cannot install secondary site %1 on server %2 because it cannot stop the SMS Bootstrap service on server %2. Possible cause: The SMS Service account for site %1 might not have the appropriate privileges to server %2. Solution: Make sure the Service account has Administrator privileges to server %2. |
|
3509 |
Error |
The sender cannot install, upgrade, or deinstall secondary site %1 on server %2. Possible cause: The server is running Windows NT %3 %4, but this does not meet the minimum installation requirements for an SMS site server. Solution: Install a version of Windows NT that meets the installation requirements. Please refer to your SMS documentation for more information. |
|
3510 |
Error |
The sender cannot install secondary site %1 on server %2. Possible cause: The server is already in use as a site system for another SMS site. Solution: Install secondary site %1 on a different server. |
|
3511 |
Error |
The sender cannot install secondary site %1 on server %2 because the sender could not copy the SMS Bootstrap service file from %3 to %4. Possible cause: The SMS Service account for site %1 might not have the appropriate privileges to create the destination file. Solution: Verify that the account has Administrator privileges to server %2. Possible cause: There is not enough free disk space on server %2. Solution: Make more space available on the destination drive. |
|
3512 |
Error |
The sender cannot install secondary site %1 on server %2 because the sender failed to install the SMS Bootstrap service. Possible cause: The SMS Service account for site %1 might not be valid. Solution: Verify that the Service account is valid. Possible cause: The Service account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the “Log on as a service” right on server %2. |
|
3513 |
Error |
The sender cannot install secondary site %1 on server %2 because the sender cannot start the SMS Bootstrap service. Possible cause: The SMS Service account for site %1 might not be valid. Solution: Verify that the Service account is valid. Possible cause: The Service account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the “Log on as a service” right on server %2. |
|
3514 |
Informational |
The sender has installed the SMS Bootstrap service on server %1. The SMS Bootstrap service will finish the installation of secondary site %2 by running SMS Setup with a script that specifies the installation parameters for site %2. You can track the progress of SMS Bootstrap by monitoring the Bootstrp.log file on server %1, and the progress of SMS Setup by monitoring Smssetup.log on server %1. |
|
3515 |
Informational |
The sender has installed the SMS Bootstrap service on server %1. The SMS Bootstrap service will finish the upgrade of secondary site %2 by running SMS Setup with a script that specifies the upgrade parameters for site %2. You can track the progress of SMS Bootstrap by monitoring the Bootstrp.log file on server %1, and the progress of SMS Setup by monitoring Smssetup.log on server %1. |
|
3516 |
Informational |
The sender has installed the SMS Bootstrap service on server %1. The SMS Bootstrap service will finish the deinstallation of secondary site %2 by running SMS Setup with a script that specifies the deinstallation parameters for site %2. You can track the progress of SMS Bootstrap by monitoring the Bbootstrp.log file on server %1, and the progress of SMS Setup by monitoring Smssetup.log on server %1. |
|
3517 |
Error |
Sender failed to send files to destination site %1. Make sure the address account has Administrator privileges to site server %2 and that site server %2 has sufficient free disk space on the SMS installation drive. |
|
3518 |
Error |
%1 failed to start. Possible cause: Server %2 might not be running RAS Server Service. Solution: Verify that server %2 is running RAS Server Service. |