valutazioni - 0, GPA: 0
(
)
)
|
da questo dispositivo ha anche altre istruzioni :
Facilità d'uso
Matrix DataBase Solution Pack for SQL Server™ Release Notes
2
• Defect 16048. When a Virtual SQL Server was moved from
Maintenance mode to Operational mode, the SQL Server service was
started on both the primary and the backup nodes.
• Defect 16087. When a Virtual SQL Server was moved to Maintenance
mode and the node was then rebooted, the command to return to
Operate mode failed because of duplicate registry keys.
• Defect 16115. A SQL Server 2000 installation failed with a log message
such as the following:
MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
16:33:05 Process Exit Code: (0)
16:33:05 p:\sql2ksp4\x86\BINN\osql.exe -Slpc:QAR14S29 -b -n -d
master -o "C:\Program Files\Microsoft SQL
Server\MSSQL\install\replsys.out" -i "C:\Program Files\Microsoft
SQL Server\MSSQL\install\replsys.sql" -E
16:33:05 Process Exit Code: (1)
16:33:05 Error running script: replsys.sql (1)
16:33:05 C:\WINDOWS\SqlSetup\Bin\scm.exe -Silent 1 -Action 6 -
Service MSSQLSERVER 16:33:20 Process Exit Code: (0) 16:33:20
Action CleanUpInstall:
16:33:20 Installation Failed.
New Installations
Refer to the PolyServe Matrix Server Installation Guide for installation
information.
Upgrade MxDB for SQL Server to the 3.4.3 Release
If your matrix is currently running Matrix Server 3.4.0 and MxDB for SQL
Server 3.4.2, use the following procedure to upgrade the servers to MxDB
for SQL Server 3.4.3.
NOTE: The Microsoft .NET Version 2.0 framework is now required for
both the 32-bit and 64-bit operating systems. The .NET framework
must be installed on all nodes.
1. Stop the MatrixServer service, using either the Services manager or the
following command:
C:> net stop matrixserver
This step forces all virtual hosts to fail over.
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
...