SQL Server Upgrade MSP Error: 29538 On KB934458 Upgrade
May 13, 2008
We have a server instance on SQL Server 2005 SP2 build 3042. We have a 32 bit x86 server. We attempted to upgrade to SP2 build 3054 KB934458. And we got the following error as stated in the Summary.txt file.
Code Snippet
**********************************************************************************
Product Installation Status
Product : SQL Server Database Services 2005 (MSSQLSERVER)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29538
Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
----------------------------------------------------------------------------------
The client tools and workstation components were successfully installed. The server is still reporting build 3042.
Here is the portions of the HotFix.log file.
Code Snippet
05/12/2008 09:19:09.041 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log
05/12/2008 09:19:09.072 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/12/2008 09:19:09.103 Registry: Cannot read registry key value "Debug"
05/12/2008 09:21:29.382 MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
05/12/2008 09:22:33.678 MSP returned 1603: A fatal error occurred during installation.
05/12/2008 09:22:33.724 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
The following version and editions have been verified.
1. .NET 2.0 installed
2. Windows XP SP2
3. MSDE 8.00.2039(SP4)
4. all MSDE databases are owned by sa
5. Instance and SQLAgent running under user that is member of Administrators
What are the possible reasons this error is occurring?
We are performing a SQL 2005 SP1 upgrade from SQL 2000 on our Windows 2003 SP1 Standard Edition.
When we run the upgrade, we got a error "Upgrade Advisor Return -1" as a pop-up window.
When we run the Upgrade Advisor separately, we get this error :
===================================
Common Language Runtime detected an invalid program.
===================================
Common Language Runtime detected an invalid program. (System.Xml)
------------------------------ Program Location:
at System.Xml.Schema.SchemaInfo..ctor() at System.Xml.Schema.XmlSchemaSet..ctor(XmlNameTable nameTable) at System.Xml.XmlReaderSettings.get_Schemas() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReportController.LoadAndValidateDataFile() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReport.ValidateDataFile() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAIssueReport.Refresh() at Microsoft.SqlServer.UpgradeAdvisor.ReportPanel.OpenReport(String reportFile)
We are in a lost for solutions. We do hope to hear from anyone asap...
We are running a test upgrade form sql 2000 standard edition 32 bit to sql 2005 developer edition 32bit. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log: Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. Database Mirroring Transport is disabled in the endpoint configuration. Starting up database 'master'. Converting database 'master' from version 589 to the current version 611. Database 'master' running the upgrade step from version 589 to version 590. Error: 946, Severity: 14, State: 1. Cannot open database 'master' version 589. Upgrade the database to the latest version. System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1 Error: 928, Severity: 20, State: 1. During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause. Error: 15151, Severity: 16, State: 1. Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
I am trying to upgrade an existing SQL Server 2000(SP3) instance to 2005.
In the installation process it showed me an existing component SQL Server 2000. But when I select the checkbox and hit the next button to upgrade the Database Engine I get an error
"Microsft SQL Server 2005 Error 1603. The setup has encountered an unexpected error while NextUpgradeDialog."
I am logged in as Administrator and have full permission.
Any help is appreciated.
Following is the Log File
Microsoft SQL Server 2005 Setup beginning at Tue Oct 09 11:30:49 2007 Process ID : 2940 E:Serverssetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2007/9/9 11:30:48 Complete: LoadResourcesAction at: 2007/9/9 11:30:48, returned true Running: ParseBootstrapOptionsAction at: 2007/9/9 11:30:48 Loaded DLL:E:Serversxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2007/9/9 11:30:49, returned true Running: ValidateWinNTAction at: 2007/9/9 11:30:49 Complete: ValidateWinNTAction at: 2007/9/9 11:30:49, returned true Running: ValidateMinOSAction at: 2007/9/9 11:30:49 Complete: ValidateMinOSAction at: 2007/9/9 11:30:49, returned true Running: PerformSCCAction at: 2007/9/9 11:30:49 Complete: PerformSCCAction at: 2007/9/9 11:30:49, returned true Running: ActivateLoggingAction at: 2007/9/9 11:30:49 Complete: ActivateLoggingAction at: 2007/9/9 11:30:49, returned true Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result. Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__2940" returned false. Running: PerformSCCAction2 at: 2007/9/9 11:30:49 Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042 Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042 Complete: PerformSCCAction2 at: 2007/9/9 11:30:50, returned true Running: PerformDotNetCheck at: 2007/9/9 11:30:50 Complete: PerformDotNetCheck at: 2007/9/9 11:30:50, returned true Running: ComponentUpdateAction at: 2007/9/9 11:30:50 Complete: ComponentUpdateAction at: 2007/9/9 11:31:44, returned true Running: DetectLocalBootstrapAction at: 2007/9/9 11:31:44 Complete: DetectLocalBootstrapAction at: 2007/9/9 11:31:44, returned true Running: LaunchLocalBootstrapAction at: 2007/9/9 11:31:44 Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1603 Aborting queue processing as nested installer has completed Message pump returning: 1603
when i open my computer and want to use SQL SERVER and when iam connecting it this error will occur "A network related or instance specific Error in SQL SERVER 2012" Then aim going to Services and Find SQLSERVER and start the services and it will connect..My Question is that why every time iam going to Start the services..I want to connect Automatically when i click on connect button in sql server its very rediculous to go evrytime in Services. i update my window 8.1 to windows 10 before it will connect automatically no need to go in services to start the SQLSERVER.
I'm getting a Windows Installer error when attempting to run the Upgrade Advisor setup package (SQLUASetup.exe). The error message reads:
"This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service."
The machine is running Windows 2000 sp4. Both the .net framework v2 and Windows Installer 3.0 have been installed.
While connecting remote SQL server through upgrade advisor I am getting the below errors:
Error: Unable to connect to server. Reason: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Pls let me know if anyone has faced this issue and know how to fix.
I have a client whose DBA upgraded their SQL 2000 database to SQL 2005. They still have it running in 8.0 compatibility mode, for various reasons, and would like me to help them develop a migration strategy to get them to full 9.0 compatibility.
My question is: can I run the Upgrade Advisor on a SQL 2005 engine database running in 8.0 compatibility mode and get anything useful? I already know there will be some issues with existing DTS packages but it would be nice to catch any other issues in advance.
I know that the Upgrade Advisor was run before the upgrade took place but to my knowledge the report was not saved and none of the recommendations were followed.
I have destroyed the cluster in failover cluster manager and then i am trying to remove node from the sql server installation centre.I am facing the cluster node and cluster service verification errors.I am not able to start the cluster service in services as well.
Am having the error below after I installed sp 2 on sql 2005. Appreciate any help on how to correct this. os is win 2003 and my account (is sysadmin) has admin privs on the server. Thanks.
Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29538 Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C:Program FilesMicrosoft SQL ServerMSSQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
We have a server which we needed to upgrade the OS on it from NT 4 Server to Windows 2000 Server.
As the system disks are seperate from the data disks. We did a fresh install of Windows, then installed SQL Server, applied service pack version 3, and then restored the master database.
From Query Analyser everything appears fine. I can query all the databases and tables, see them all, the web applications talk the database fine so all the users have recreated OK.
However .... if we try and look at the database through management console we get the following error.
A connection could not be established to ....
Reason: Cannot resolve collation conflict for like operation..
This happends logged in locally to the machine as administrator as well as connecting remotely. Does anybody have any idea what is happening?
I am trying to upgrade from SQL Server 2000 SP4 to SQL Server 2005. But I am getting an error saying that " Your operating system does not meet service pack requirements for the SQL server release. Install the service pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkID=50380, and then run the SQL Server Setup again. For system requirements, see hardware and software requirements, in the readme or in SQL Server Books online."
I don't know what other service pack I would need to upgrade to again when I already have SP4 installed. Could someone tell me what I need to do next.
We have an old 16-bit app that runs fine in SQL 7.0 but on our test SQL 2000 box some reports generate the following error "System Message 10202 - The application fetch buffer size is less than the cursor select statement requires". Any ideas what this means, I am not much of a coder. The MS Knowledge base does not list much on this.
I am having the following error when running the SQL upgrade wizard trying to upgrade SQL 6.5 to SQL 2000. Does anyone here know what is the problem ?
Version Switch has aborted because you do not have "Full Control" permission to one of the HKEY_LOCAL_MACHINESoftwareMicrosoftMSSQLServ* registry keys. Please use regedit32.exe to correct this problem and try again.
I have already checked the registry and I do have full control permission on HKEY_LOCAL_MACHINESoftwareMicrosoftMSSQLServ*. Please help.
I launch an installatino of SQL Server 2000 on a server, upgrading the V7 original datbase but it failed with error : "the ordinal 105 could not be located in the dynamic link library opends60.dll"
I have upgraded many of my servers from 2000,SP2 to 2005. Whilst doing 1 server I have the following error message:
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation..To continue, correct the problem, and then run SQL Server Setup again.
I have tried to search in many places for this error whilst upgrading but found none, please help.
I am having an issue running a SP4 upgrade for SQL Server 2000. The sp_vupgrade_replication.out file indicates: Msg 170, Level 15, State 1, Server MS, Line 1 Line 1: Incorrect syntax near '-'.
The sqlsp.log file indicates: Process Exit Code: (0) Error running script: sp_vupgrade_replication (1) Action CleanUpInstall: Installation Failed.
I'm carrying out an investigation into how much effort will be involved in upgrading our database from SQL Server 7.0 to SQL Server 2005. I've downloaded the Upgrade Advisor and run in against a copy of our production database. Most of the issues are trivial and I understand how to resolve them apart form one (to me) meaningless one:
When to Fix : Before
Description : Class Not Registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
Details : SVCACCTREQ
That's all the information it gives, except for a "This issue is resolved" checkbox. Anyone got any idea what the problem is, or how I go about tracking down the cause?
I'm running the analysis tool from a W2K Professional Client, connecting to SQL Server 7.0 running on an NT4 Server using Windows authentication. The account I'm connecting with is a member of the System Administrator group in SQL Server and is a local admin on the client, and a member of the Users group on the server.
I just tried to install SP1 for SQL 2005. All of the steps succeeded except for the upgrade for Reporting Services, which failed with the error "Unable to install Windows Installer MSP file". When I checked the log there were a whole host of errors such as
"12/19/2006 09:06:41.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesReportManagerBinja eportingserviceswebuserinterface.resources.dll"
and
"12/19/2006 09:06:41.203 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesReportManagereshelpf1_rsc_webui_standalone_5yr5.htm"
and
"12/19/2006 09:06:47.093 Failed to read registry key: Debug"
I am running a default instance, and was running the install under an account with local admin privileges.
I am trying to upgrade SQL 2000 SP3 to SQL 2005 SP2 on a Windows 2003 server with all the latest patches. The SQL 2005 install went through like it was supposed to but when it was nearly finished it gave the message: " there was an unexpected failiure during the setup wizard. You may review the setup logs and/or click the help button for more info". I'm pretty new to Microsoft SQL so I looked at help and there was no information.
I've tried running setup again and keep getting the above error message. During the install the program says everthing is installed but I've noticed the Management Center is missing.
I have a SQL6.5 sp5a, NT4 sp5, BDC, IE5 server that I have installed SQL7 on. My installation is set to mixed security.
Everytime I try to run the upgrade wizard I get the following error/problem right after the "Checking 6.x syscomments for corruption and Verifying 6.x data base logins etc.
Summary of warnings (if any) and choices:
============================================= The following syscomments entries are invalid on your 6.x SQL Server. It is recommended that you fix these problems before you continue. ============================================= ******************************** master ******************************** ********************************
Inconsistency Report For Database: master. ********************************
dbo.sp_db_upgrade2
Procedure
Occurs 28 times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system catalogs not enabled. System Administrator must reconfigure system to allow this.
--------------------------------
dbo.sp_fallback_activate_svr_db
Procedure
Occurs three times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system catalogs not enabled. System Administrator must reconfigure system to allow this.
--------------------------------
dbo.sp_password
Procedure
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system catalogs not enabled. System Administrator must reconfigure system to allow this.
--------------------------------
dbo.sp_recompile
Procedure
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system catalogs not enabled. System Administrator must reconfigure system to allow this.
--------------------------------
dbo.sp_rename
Procedure
Occurs 11 times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system catalogs not enabled. System Administrator must reconfigure system to allow this.
--------------------------------
============================================= The following script will be created as upgrade.ini and run into the script interpreter when you press finish. ============================================= [Options] Method=1 Perform a CRC Check=0 Source=CCIDEV Destination=CCIDEV Export Server Startup Options= Import Server Startup Options= -T1808 SQLServer70Path=C:MSSQL7SourcePassword=066ce2f9c0e 4ba DestinationPassword=00 MasterPath=C:MSSQLDATAMASTER.DAT VerswitchOldVer=65 Code Page=1252 Override Server Code Page=0 QuotedIdentifiers=0 ObjectDumpPath=c:mssql7upgradeCCIDEV_071399_163117 Ansi Nulls=0 [Tasks] Export and Import via Named Pipe=0 Marking database upgrade status=0 Export Logins=0 Export Database Owners=0 Import Logins=0 Creating Databases=0 Setting Database Options=0 Export Database Objects=0 Import Database Objects=0 Export SQL Executive Settings=0 Preparing MSDB for Upgrade=0 Import SQL Executive Settings=0 Export Server Settings from Master=0 Modifying Scripts=0 Import Server Settings from Master=0 Preparing SQL-DMO for upgrade=0 [Databases] 006CCIDATA=0 003model=0 005msdb=0 001master=0
I don't find anything about this anywhere except the upgrading to SQL7 white paper, it mentions that the text for objects must be intact in the syscomments system table and that logins must exist for every database user, but that doesn't really tell me how to fix this.
Has any one seen these errors or can point me to where on Microsoft's site you can now EASILY get KB info for SQL Server 7?
I upgraded to SQL Server 2005 SP2 release today. I had been working with 9.00.1399. I had developed few packages in the older version which were getting invoked through the asp web application locally and it was working fine.
Today I upgraded to SQL server 2005 3042 version. Now the same packages are not working when invoked through the web application. But it works fine stand alone. All errors refer to connection problem.
I need to resolve this urgently. Can anyone help me please?
Errors -
"SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "The Microsoft Jet database engine cannot open the file ''. It is already opened exclusively by another user, or you need permission to view its data.". "
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
We setup a new Shared SQL server 2014 Web and transferred all SQL databases over. However when customers connect via SQL Management Studio they now get VIEW STATE error when right clicking on any table on any database.
I got the following error using either NT or SQL Login ('sa') that are sysadmin in my SQL 2005 instance:
Your Account information could not be verified for one or more instances. Ensure that you can connect to all the selected instances using the account information provided. To process further deselect the instances to which connectivity cannot be established.
However, I would login to SQL 2005 named instance, either NT or SQL login 'sa' without any problems to do anything I want because both are sysadmin.
<PS> Note that my default SQL instance in my local server is SQL 2000 and SQL 2005 named instance.
Unable to connect to server. Reason: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)
When I'm trying to create a database diagram for my tables., First it prompts me saying that - "This database does not have one or more of the supported objects... Do you wish to create them? I know this is normal when you don't have any diagrams. But after clicking "Yes", I get the following error which is attached.
I tried changing the database Owner to "sa". But, still the same error. Interestingly, other databases that are already having the database diagrams (created by others), are allowing me to create new diagrams in those databases. The only difference is, I created this database where I'm trying to create diagrams on. How do I get this working.
I am trying to enable FILESTREAM on a SQL 2012 installation that is supporting a Sharepoint 2013 implementation. When I try to enable FILESTREAM using the SQL Server Configuration Manager I receive the following error:
There was an unknown error applying the FILESTREAM settings. Check the parameters are valid. (0x80041008)
I have done this succussfully in the past in SQL2008R2/Sharepoin2010 environment but this is my first attempt with SQL2012/Sharepoint2013 and I am not sure how to proceed with troubleshooting.
SQL 2000 to SQL 2005 Upgrade Error - Database Down - Help Appreciated
I am upgrading a SQL 2000 standard database server to SQL 2005 standard on a windows 2003 server
I am logged in as domain admin and started the upgrade as 'sa'
The upgrade stops with the error:
Service MSSQLSERVICE can not be started. Verify you have sufficient privilages to start system services. The error code is (17185)
The error log shows:
2007-01-04 15:59:38.77 Server Authentication mode is MIXED.
2007-01-04 15:59:38.79 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-01-04 15:59:38.79 Server (c) 2005 Microsoft Corporation.
2007-01-04 15:59:38.79 Server All rights reserved.
2007-01-04 15:59:38.79 Server Server process ID is 4188.
2007-01-04 15:59:38.79 Server Logging SQL Server messages in file 'F:SQLDataMSSQLlogERRORLOG'.
2007-01-04 15:59:38.79 Server This instance of SQL Server last reported using a process ID of 2980 at 1/4/2007 3:56:58 PM (local) 1/4/2007 2:56:58 AM (UTC). This is an informational message only; no user action is required.
2007-01-04 15:59:38.79 Server Registry startup parameters:
2007-01-04 15:59:38.79 Server -d F:SQLDataMSSQLdatamaster.mdf
2007-01-04 15:59:38.79 Server -e F:SQLDataMSSQLlogERRORLOG
2007-01-04 15:59:38.79 Server -l F:SQLDataMSSQLdatamastlog.ldf
2007-01-04 15:59:38.79 Server Command Line Startup Parameters:
2007-01-04 15:59:38.79 Server -s MSSQLSERVER
2007-01-04 15:59:38.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-01-04 15:59:38.79 Server Detected 4 CPUs. This is an informational message; no user action is required.
2007-01-04 15:59:38.83 Server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
2007-01-04 15:59:39.02 Server Using the static lock allocation specified in the locks configuration option. Allocated 20000 Lock blocks and 20000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-01-04 15:59:39.02 Server Multinode configuration: node 0: CPU mask: 0x0000000a Active CPU mask: 0x0000000a. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2007-01-04 15:59:39.04 Server Multinode configuration: node 1: CPU mask: 0x00000005 Active CPU mask: 0x00000005. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2007-01-04 15:59:39.04 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-01-04 15:59:41.04 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-01-04 15:59:41.04 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-01-04 15:59:41.04 spid7s Starting up database 'master'.
2007-01-04 15:59:41.05 spid7s 1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2007-01-04 15:59:41.07 spid7s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2007-01-04 15:59:41.07 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2007-01-04 15:59:41.08 spid7s SQL Trace ID 1 was started by login "sa".
2007-01-04 15:59:41.08 spid7s Starting up database 'mssqlsystemresource'.
2007-01-04 15:59:41.11 spid7s Using 'dbghelp.dll' version '4.0.5'
2007-01-04 15:59:41.11 spid7s ***Stack Dump being sent to F:SQLDataMSSQLLOGSQLDump0035.txt
2007-01-04 15:59:41.11 spid7s SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2007-01-04 15:59:41.27 spid7s Unable to update password policy.
2007-01-04 15:59:41.27 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Unhandled Exception: System.Security.SecruityException: Request failed. at Microsoft.SqlServer.Chainer.Setup.Setup.DebugBreak() at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
Then the Managed SQL Server Installer box pops up with Managed SQL Server Installer has stopped working.
I am currently in the process of upgrading a server from 6.5 to 7.0 However I am using the sp_dbcmptlevel stored procedure to leave the database in 6.5 compatability mode.
I have a few urgent questions on this:
- Would leaving a database in 6.5 affect database performance,ability to use web based development, datawarehousing?
- If I wanted to upgrade to SQL Server 2000, would I first have to switch compatability to 7.0 and then upgrade to 2000?
I would really appreaciate anyone with knowledge on these issues.
