Cause:  You may receive this error when you try to install SQL Server 2000 Service Pack 3. It occurs when the Service Pack 3 Setup program tries to copy Setupsql.ini to the %Temp% folder, but cannot overwrite a pre-existing version of the file that is marked as read-only.

Solution:  Browse to the %Temp% folder on your system drive, and either delete the pre-existing version of setupsql.ini or remove the read-only attribute. Then run SQL Server 2000 Service Pack 3 Setup again.

Cause:  A user account has reached the assigned Exchange mailbox size limit.

Solution:  Save e-mail messages in a local folder on the client computer. If this problem occurs often, consider increasing the mailbox size for the user account.

Cause:  The user account has reached the assigned disk quota limit.

Solution:  Save files in a local folder on the client computer. If this problem occurs often, consider increasing the disk quota for the user account.

Cause:  The user account password does not comply with a password policy configured by the administrator.

Solution:  Create a new password that complies with the password policies configured by the administrator.

Cause:  The user does not have permissions to log on by using Remote Desktop.

Solution:   Assign the user permissions to use Remote Desktop.

Cause:  The client computer running Windows XP Professional is not configured to allow Terminal Services connections.

Solution:  Configure the client computer running Windows XP Professional to use Remote Desktop.

Cause:  There may be too many failed logon attempts.

Solution:  Unlock the user account.

Cause:  Service account passwords have been changed but automatic logon properties have not been updated to use the new passwords. Windows Small Business Server does not automatically propagate password changes to all applications that use the service account.

Solution:  Update the service accounts and passwords used with a particular application by running Windows Small Business Server Setup again.

Cause:  A new user attempts to log on or access network resources immediately after the account is created and before Active Directory has had time to update. A delay can occur between the time a user account is created and when Active Directory recognizes the user account.

Solution:  Wait fifteen minutes and try again.

Cause:  This problem can occur if a user account name contains Unicode characters.

Solution:  Use the Active Directory Users and Computers snap-in to change the SMTP e-mail address for the account.

The Setup program for Windows XP Service Pack 2 (SP2) requires that your computer uses AC power. If the battery power runs out during installation, the update cannot be completed. If this occurs, you might not be able to restore the operating system to its previous state.

Solution:  To resolve this issue, connect your computer to an AC power source, such as an electrical outlet, and then run Setup.

For more information about this issue, see Article 883609, "This Service Pack requires the machine to be on AC Power before setup starts," at the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=70662).

Cause:   If you made user profiles private, administrative credentials were removed from user folders on the client computer. Users need these credentials to access folders that are redirected to the server. After you migrate private user profiles (which include redirected folders), users may be unable to access their folders.

Solution:  Manually restore access to user folders on the client computer.

Cause:  This error occurs when one or more of the subfolders in a user's profile have been made private. This means that permissions giving other users access to the folders have been removed.

Solution:  Manually configure the client computer to remove the restrictions that are preventing the migration.

If the client computer is running Windows XP Professional, make sure that the profile that did not migrate is configured as a "public" profile.

Cause:  If applications other than those available by default were installed on client computers, they will not be upgraded.

Solution:  You must reinstall these applications on the computer running Windows Small Business Server 2003 and then reinstall them on client computers after the upgrade is complete. Command lines used to install these applications are stored in the registry in the following location:

HKLM\SOFTWARE\Microsoft\SmallBusinessServer\clientsetup\sbs2k_archive\Client Applications\

After the upgrade is complete, start the Client Setup Applications Wizard and use the command lines to reinstall the applications.

Cause:  Older versions of Office conflict with Office 2003.

Solution:  To run older versions of Office, you must uninstall all versions of Office on the client computer, and then reinstall the version you want to use.

Cause:  Redirection for My Documents folder has been enabled, and a large amount of data in the My Documents folder on the client computer is synchronizing with the server.

Solution:  No action is required. After the initial logon, only changes to the My Documents folder are synchronized. Synchronization does not take as long as the initial logon.

Cause:  Disk quotas have been exceeded.

Solution:  Reduce the size of the user's My Documents folder by deleting unnecessary files or compressing files. Or, increase the quota amount.

Cause:  This error occurs when one or more of the subfolders in a user's profile have been made private. This means that permissions giving other users access to the folders have been removed.

Solution:  Manually configure the client computer to remove the restrictions that are preventing the migration.

If the client computer is running Windows XP Professional, make sure that simple file sharing is enabled on the computer, and then follow the steps outlined in the error message.

If the client computer is running Windows 2000 Professional, log on to the client computer as the user with the profile that did not migrate, and then grant the Administrators group full control over the profile folder and all subfolders.

Cause:  If a mobile device is connected to the client computer, ActiveSync cannot be completely installed.

Solution:  Disconnect the mobile device from the client computer, log off, log on again, and then reinstall ActiveSync.

For more information, open Help and Support and search for "To connect a mobile device by using a cradle or cable."

Cause:  The server is configured to connect to the Internet using a dialup connection instead of a broadband connection.

Solution:  Configure the Pocket PC 2003 using the instructions that came with your device, and manually configure it to synchronize with the server. You must also disable Secure Sockets Layer (SSL) on the mobile device.

Cause:  This problem can occur if any of the following conditions are true:

• The server is not connected to the Internet.
  
  
• The server is connected to the Internet using a dial-up connection.
  
  
• The user has configured ActiveSync to synchronize the mobile device with the server.
  
  

Solution:  Manually configure ActiveSync to synchronize with the desktop computer.

Cause:   If the server is configured with a single network card and a hardware firewall, routers that have built-in IP spoofing protection do not allow internal client computers to connect to the external domain.

Solution:  Consult with your hardware provider for updated firmware for your specific device. As an alternative, you can add a DNS zone to bypass IP spoofing by some hardware routers.

Cause:  ActiveSync cannot create Microsoft Office Outlook 2003 profiles. If the user starts ActiveSync before running Outlook 2003, the user receives an error message stating that the profile cannot be found.

Solution:  Connect the mobile device by using the cradle or cable, open Outlook, and then reconnect the mobile device.

Cause:  If you connect the mobile device by using a cradle or cable, you are considered anonymous when browsing the Internet. If ISA Server is installed on the computer running Windows Small Business Server 2003, anonymous browsing is not allowed.

Solution:  Follow the instructions for Microsoft Pocket PC Phone Edition 2002, Microsoft Pocket PC Phone Edition 2003, or Microsoft SmartPhone 2003, and then follow the instructions to configure ActiveSync settings.

Cause:  There is a universal serial bus (USB) connection error.

Solution:  Upgrade to the latest version of ActiveSync. If the user is already using the latest version, remove the mobile device from the cradle (or disconnect the cable), turn the device off and then back on, and then reconnect it.

Cause:  The Pass Through option is not configured correctly in ActiveSync.

Solution:  Configure the Pass Through option.

Cause:  Some of these devices are not supported using the Windows Small Business Server unsigned certificate.

Solution:  Purchase a signed certificate from a trusted certification authority (CA) for the server to support these devices.

If you continue to have a problem using your mobile device, consider the following questions:

• Does your mobile device have sufficient signal strength?
  
  
• Can you browse to other internal or external Web sites?
  
  
• Have you tried turning off the device and then turning it back on?
  
  
• Does your mobile device synchronize when connected to the server?
  
  
• Have you allowed access to the Outlook Mobile Access Web service from the Internet using the Configure E-mail and Internet Connection Wizard?
  
  
• Are you using an external router? Are ports 80 and 443 open and pointed to the server?
  
  
• Have you tried reconfiguring your mobile device?
  
  

For more information, open Help and Support and search for "To allow access to Web services on the server.

Cause: You may not have selected the folder or the parent folder from where the item was permanently deleted.

Solution: If you are recovering a permanently deleted mail item, ensure that you select the folder from which the mail was deleted. For example, if you have a subfolder in your Inbox named Meeting Minutes, you must select the Meeting Minutes folder before you choose the Recover Deleted Items option on the Tools menu.

If you are recovering a deleted folder, ensure that you select the parent folder of the deleted folder. For example, if you permanently deleted a subfolder named Meeting Minutes from your Inbox, you must select the Inbox folder before you choose the Recover Deleted Items option on the Tools menu.

Cause: There are two possible causes. First, you may be using Outlook over the Internet (which is also called "RPC over HTTP") to check your e-mail. Second, you may have manually joined the Windows XP-based client computer t o the Windows Small Business Server network. If you did, then you bypassed Windows Small Business Server Client Setup, which enables the Recover Deleted Items option in Outlook.

Solution: You must manually enable the Recover Deleted Items option.

Cause:  The Configure E-mail and Internet Connection Wizard can configure reply-to addresses for only one e-mail domain on the E-mail Domain page.

Solution:  Use one of the e-mail domain names when you run the wizard. Then, you can create a custom recipient policy in Exchange Server 2003 for a second e-mail domain. The custom recipient policy creates the appropriate e-mail addresses for users in the second e-mail domain.

For more information, search for "Create a New Recipient Policy" in Exchange server Help. To access Exchange server Help, click Start, click Server Management, and then press F1.

Cause:  Connection filtering is not configured on your Exchange server.

Solution:  Exchange 2003 supports connection filtering based on block lists, which are lists that can be queried by your Exchange server to identify verified spam sources. Connection filtering uses external services that list known sources of unsolicited e-mail, dial-up user account lists, and servers open for relay based on IP addresses on block lists that they maintain. Connection filtering complements third-party content filter products. You can also configure connection filtering without using a block list provider by creating global accept and deny lists of SMTP addresses from which you want to globally accept or deny all e-mail.

To configure connection filtering, you must first create and configure a connection filtering rule, and then apply it your SMTP virtual server. For more information, search for "Configure Connection Filtering" in Exchange server Help. To access Exchange server Help, click Start, click Server Management, and then press F1.

Cause:  A user has repeatedly tried to log on due to losing or forgetting the user account password. This alert occurs when the number of failed logons for a specific user exceeds the Account Lockout Threshold.

Solution:  Reset the user account password.

Cause:  An actual attack has occurred. This alert occurs when the number of failed logons for a specific user exceeds the Account Lockout Threshold.

Solution:  You need to do the following if you suspect the account is under attack:

• Unplug the Internet cable from your server or router if you are certain that your network has been attacked. Open Event Viewer and view the audit logon events in the Security Events log to determine if an attack has occurred.
  
  

• View the event log to try and determine the IP address from which the attack is originating. Contact your Internet service provider (ISP) to report or block it.
  
  
• Check for any unknown user accounts by using the Manage Users snap-in in Server Management.
  
  
• Reset the user's password.
  
  
• Reset the administrator password.
  
  
• Disable the user account until the threat of the network attack passes.
  
  

• Consider setting strong password policies.
  
  

For more information about keeping your network secure, visit the Microsoft Security and Privacy Web site (http://go.microsoft.com/fwlink/?LinkID=102).

Cause:  You might be using a router as a firewall to access the Internet. If so, usage information for Internet activity cannot be included in the report because Windows Small Business Server 2003 is unable to monitor firewall statistics for third-party devices.

Solution:  Install a second network adapter on the computer running Windows Small Business Server 2003, and then enable the Routing and Remote Access service as the firewall on the server by using the Configure E-mail and Internet Connection Wizard.

Cause:  You might be using the Internet Security and Acceleration (ISA) Server firewall to access the Internet. Windows Small Business Server 2003 is unable to monitor firewall statistics for ISA Server.

Solution:  Configure ISA Server for monitoring and reporting. For more information about configuring ISA Server for monitoring and reporting, search for "Configure monitoring and reporting" in the ISA Server Help. To access ISA Server Help, click Start, click Server Management, and then press F1.

Cause:  By default, Outlook Express blocks certain file attachments in e-mail to prevent you from opening potentially harmful attachments. As a result, you may not be able to open server performance or usage reports.

Solution:  Configure Outlook Express to allow attachments.

Cause:  If a selected log file has not changed since the last time it was attached to a server performance or usage report, or if no new files exist for applications that generate multiple log files (such as Internet Information Services), the server performance or usage report will not contain attachments for those selections.

Solution:  No action is required. To review the latest version of a selected log file, open the file attachment from the previously delivered server performance or usage report.

Cause:  When configured to start automatically, a small number of services may stop running if they are not performing any tasks. When this happens, these services are reported in the server performance report as not running. This is known to occur with the following services:

• Fax
  
  
• Performance Logs and Alerts
  
  
• Removable Storage
  
  

Solution:  The noted services are designed to stop running when they are not being used. If you do not want these services to be reported in the server performance report when they are not running, you can change the Startup type for the service to Manual.

For more information, open Help and Support and search for "Monitoring overview."

Cause:  After a Health Monitor configuration is imported using the Import Health Monitor Configuration Wizard, imported actions may not run as expected. This problem can occur when settings for imported actions remain associated with the computer from which they were exported. For example, the SMTP server specified for e-mail actions could be inaccurate, or an inaccurate file path could be specified for script actions.

Solution:  Review the settings for the imported actions and make changes as necessary.

For more information, open Help and Support, and then search for "To update settings for an imported Health Monitor configuration."

Cause: If your server is running Internet Security and Acceleration (ISA) Server, then at midnight ISA Server creates a new MSDE instance to store the next day's logging information for the Web and proxy traffic. If a backup is also a scheduled to begin at midnight, there is a conflict between the ISA Server MSDE instance and the backup process, and this conflict causes the server to lock down.

Solution: To exit the lockdown, restart the Microsoft Firewall service.

To prevent this issue in the future, schedule the server backup to start at either 11:30 P.M. or 12:30 A.M. This ensures that there is no conflict between the ISA Server MSDE instance and the backup process.

Cause: If the quarantine folder for your antivirus software is saved to a volume that is protected by a previous version of Volume Shadow Copy service, then the shadow copy captures the quarantine folder. As a result, the shadow copy includes viruses.

Solution: You can either use the antivirus software to move the quarantine folder to a volume that is not protected by Volume Shadow Copy service or configure the anti-virus application to delete infected files instead of having them quarantined.

For more information about resolving this issue, if you are using TREND Micro, Inc. antivirus software on your server, see Article 888035, “Quarantined virus files are skipped and your backup reports a failed status on your Windows Small Business Server 2003-based computer” at the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=70319).

Cause:  You have not configured a back up solution for your mailbox database.

Solution:  Use the recovery storage group feature in Exchange Server 2003 to create a backup copy of the Exchange mailbox database on the server. You can do this while the original database is still running and serving client computers. For information about how to create a backup copy of the Exchange mailbox database on the server, see "Using Microsoft Exchange Server 2003 Recovery Storage Groups" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=70663).

Cause: NTBackup.exe is being manually ended from the Task Manager, or NTBackup.exe encountered an error during launch.

Solution:  Run NTBackup manually, and load the Small Business Backup Script.

If the backup succeeds, run the Windows Small Business Server Backup Configuration Wizard from the Backup taskpad in Server Management. If the problem persists, click Start, click Server Management, click the Information Center link, and then click either Community Website or Technical Support to get information about the problem.

If the backup fails, consult the error message for further information about the problem.

Cause:  The Exchange Information Store is not running.

Solution:  Start the Exchange Information Store.