When a pop-up message is received from Backup Exec 7.0 build 719 that is installed on Windows NT Server 4.0, the access to the CPU is blocked, except for critical processes necessary to keep the computer running Windows NT running. Some or all applications may quit responding until the message box is closed. The server may become completely unresponsive on the network while in this state.

NOTE: This behavior has only been seen in Backup Exec 7.0 Build 719.

Back to the top

Seagate Technical Support reports that Build 719 of Backup Exec for Windows NT Server 7.0 makes a change to the registry that causes this behavior. The registry change is required in order for Backup Exec to work on Small Business Server (SBS). This change, however, causes problems on Windows NT 4.0 Server. At this time, the installation program of Build 719 does not check to see if the version of the OS is Windows NT Server or BackOffice SBS. The registry subkey changed is:

The entry before installing Backup Exec 7.0 Build 719 is: The entry after installing Backup Exec 7.0 Build 719 is:

Back to the top

On Windows NT Server 4.0, add the "=16" value back to the MaxRequestThreads section. Do not make this change on Small Business Server.

Back to the top

Build 719 removes the "=16" from MaxRequestThreads=16. Also note that Backup Exec implements the change indicated in the following article by adding ",512" after the SharedSection:

For additional information, please see the following article in the Microsoft Knowledge Base:

For information on Backup Exec, see the following Web site: The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Back to the top