I've got a box running Windows 2000 Server and SQL Server 2000. This summer I plan on upgrading to Windows 2003 Standard and SQL Server 2005, but which do I do first?
My guess is that I shouldn't mess with upgrading SQL at all. Just dump the data, uninstall, upgrade the OS, install SQL 2005 and reimport the data back in. Is that a really bad idea?
I would think that if I wanted to upgrade both, then Windows should be upgraded first, right?
Hello, I have to do an upgrade from server 7 and OS NT to server2000 and windows 2000. Has anyone had any problems while doing this ? Please list the steps taken for the upgrade if you can. Thanks
I posted this under 'microsoft.public.sqlserver.client' but got no reply.Any help with this problem would be greatly appreciated---------------------I developed a database under SQL Server 2000, with Access 2000 on Windows2000 as client. This had been running fine for several years. The client isnow upgrading to Windows XP, and has come across a display problem on thereports. The figures are correct but are now displayed with lots of trailingzeros e.g365.00000I have built a test system but cannot duplicate the problem :-( . Also theproblem varies between computers, and even between different users on thesame computer. One solution that seems to work is to explicitly cast alloutput from the server e.g.CAST ( TonsLoaded AS INT) TonsLoadedbut this is a pita since there are 141 stored procedures.Has anyone seen this problem? I haven't found anything in the newsgroups orany Knowlege Base article. It looks like it is to do with Windows XP as theclient ...David
This morning I attempted to connect to my local copy of SQL Server (2012) (Win 7) using Windows Authentication. I was unable to do so and per the error log it was due to error 18456 (invalid credentials).
Yesterday I changed my windows password. Is it possible for this to be the cause?
FYI, following is from the error logs:
2015-04-27 10:10:32.98 Backup BACKUP DATABASE successfully processed 0 pages in 0.451 seconds (0.000 MB/sec).2015-04-28 00:00:41.90 spid18s This instance of SQL Server has been using a process ID of 2096 since 4/21/2015 9:08:05 AM (local) 4/21/2015 1:08:05 PM (UTC). This is an informational message only; no user action is required.2015-04-28 09:58:51.16 Logon Error: 18456, Severity: 14, State: 38.2015-04-28 09:58:51.16 Logon Login failed for user 'NT AUTHORITYSYSTEM'. Reason: Failed to open the explicitly specified database 'model'. [CLIENT: xx.xx.xxx.xxx]2015-04-28 17:09:59.87 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
The logs showed the error occurred yesterday (4/28) which is about when I changed my password. The 17:09 log (last one) is when I shut down my computer. Note that I was logged into SQL Server when I changed my Windows password and worked with it several times through out the day.
Also, per the configuration manager SQL Server (MSSQLSERVER) (and all other services) is stopped and I was unable to start it ("The request failed or the service did not respond in a timely fashion).
I "upgraded" to Windows 10 (I was installing a new c: drive anyway). I installed SQL Server & SSIS, Visual Studio 2012, SQL Server Data Tools 2012, etc. When I try to load up my project (.sln) in SQL Data Tools I get the following warnings/errors:
Warning 1 Warning loading DataImport.dtproj: Warning: Failed to decrypt an encrypted XML node. Verify that the project was created by the same user. Project load will attempt to continue without the encrypted information.
Warning 2 Warning loading DataImport.dtproj: Warning: Failed to decrypt sensitive data in project with a user key. You may not be the user who encrypted this project, or you are not using the same machine that was used to save the project. If the sensitive data is a parameter value, the value may be required to run the package on the Integration Services server.
Error 3 Error loading ImportFiles.dtsx: The version number in the package is not valid. The version number cannot be greater than current version number.
Error 4 Error loading ImportFiles.dtsx: Package migration from version 8 to version 6 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.".
Error 5 Error loading ImportFiles.dtsx: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">8</DTS:Property>" from node "DTS:Property".
Error 6 Error loading 'ImportFiles.dtsx' : The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
As well as installing Windows 10, I had also renamed by computer. I have tried renaming it back (I noticed some references to the computer name in the xml), but no difference.Have I installed the wrong versions of one of the software? If so, how could I check which one I need to install (to match the VS project/dts package)?
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.
SQL Server 2005 x64 Developer Edition Log output from the SP2 installation... ------------------------------------------------------------------------------------------------ Product : Database Services (MSSQLSERVER) Product Version (Previous): 2221 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 11032 Error Description : Unable to install Windows Installer MSP file ------------------------------------------------------------------------------------------------
The C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log file is a 5mb file that I can't make much sense out of...here are the first many lines of the file. I'll be glad to provide more information - just let me know what you need to know... Thanks, Dave
=== Verbose logging started: 8/15/2007 20:32:13 Build type: SHIP UNICODE 3.01.4000.4042 Calling process: e:47b31966cf7dcaa4e0fe0fa356ab34dahotfix.exe === MSI (c) (D4:9C) [20:32:13:508]: Resetting cached policy values MSI (c) (D4:9C) [20:32:13:508]: Machine policy value 'Debug' is 0 MSI (c) (D4:9C) [20:32:13:508]: ******* RunEngine: ******* Product: {F14F2E25-99AF-42A9-977C-F6D0352DC59F} ******* Action: ******* CommandLine: ********** MSI (c) (D4:9C) [20:32:13:508]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (D4:9C) [20:32:13:508]: Grabbed execution mutex. MSI (c) (D4:9C) [20:32:13:508]: Cloaking enabled. MSI (c) (D4:9C) [20:32:13:508]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (D4:9C) [20:32:13:508]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (9C:BC) [20:32:13:539]: Grabbed execution mutex. MSI (s) (9C:FC) [20:32:13:539]: Resetting cached policy values MSI (s) (9C:FC) [20:32:13:539]: Machine policy value 'Debug' is 0 MSI (s) (9C:FC) [20:32:13:539]: ******* RunEngine: ******* Product: {F14F2E25-99AF-42A9-977C-F6D0352DC59F} ******* Action: ******* CommandLine: ********** MSI (s) (9C:FC) [20:32:13:539]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (9C:FC) [20:32:13:539]: Adding MSIINSTANCEGUID to command line. MSI (s) (9C:FC) [20:32:13:539]: End dialog not enabled MSI (s) (9C:FC) [20:32:13:539]: Original package ==> C:WINDOWSInstaller1f00a5.msi MSI (s) (9C:FC) [20:32:13:539]: Package we're running from ==> C:WINDOWSInstaller1f00a5.msi MSI (s) (9C:FC) [20:32:13:586]: APPCOMPAT: looking for appcompat database entry with ProductCode '{F14F2E25-99AF-42A9-977C-F6D0352DC59F}'. MSI (s) (9C:FC) [20:32:13:586]: APPCOMPAT: no matching ProductCode found in database. MSI (s) (9C:FC) [20:32:13:586]: Detected that this product uses a multiple instance transform. MSI (s) (9C:FC) [20:32:13:586]: MSCOREE not loaded loading copy from system32 MSI (s) (9C:FC) [20:32:13:586]: Applying multiple instance transform 'qlRun01.mst'... MSI (s) (9C:FC) [20:32:13:586]: Looking for storage transform: SqlRun01.mst MSI (s) (9C:FC) [20:32:13:586]: Validating transform 'SqlRun01.mst' with validation bits 0x809 MSI (s) (9C:FC) [20:32:13:586]: Transform 'SqlRun01.mst' is valid. MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2205 2: 3: Patch MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2205 2: 3: PatchPackage MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Media 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: File 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary. MSI (s) (9C:FC) [20:32:13:586]: TRANSFORM: Applying regular transform to database. MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Validation 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: File 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: MsiFileHash 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: RegLocator 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: AppSearch 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: CompLocator 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: DrLocator 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Directory 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Registry 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Condition 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: CreateFolder 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _sqlObjectSecurity 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Icon 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038 ...
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"
I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.
My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.
I enabled all the protocols and all the ports I disabled windows firewall and antivirus (eset nod32) I installed all service packs available I have also installed Visual Studio 2005 without installing sqlexpress
But nothing happens!
Please i am very desperate, any information will be gratefully accepted.
This is my installation Information
Code Snippet
Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft MSXML 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.6001.18000 Microsoft .NET Framework 2.0.50727.1434 Operating System 6.0.6001
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 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 am attempting to write a Windows service that watches a database for uploaded files to import. When a new file is found, the corresponding SSIS package is run from the file system with variables passed through. I started development as a Windows app and copied the functionality to a service.
The app runs fine. The service does not. I get a "Failure" each time a package is executed. Everything is identical behind the scenes with the obvious exceptions that OnStart and OnStop handlers are buttons in the app. I added a script task at the beginning of one of the SSIS packages to notify me that it is even running at all. It doesn't even hit that initial task.
Again, the app will run all packages just fine. The data is imported and the results return as "Success."
The following is the code executing the package. Any help is appreciated. I've been banging my head on this one for a few days now. (Is there a tag to format a code sample?)
Dim pkgLocation As String Dim pkg As New Package Dim app As New Application Dim pkgResults As DTSExecResult
Have two C# applications - one WinForms desktop app, the other a WinForms smart device app. Both use SQL Server Compact CE 3.5 to store data locally. Both work just fine.
Now the desktop app needs to open and update the .SDF file that is stored on the Windows Mobile device. (Device will be docked via USB.)
What format would the path to the .SDF look like that the WinForms application would need to specify in order to open it?
My server is a dual AMD x64 2.19 GHz with 8 GB RAM running under Windows Server 2003 Enterprise Edition with service pack 1 installed. We have SQL 2000 32-bit Enterprise installed in the default instance. AWE is enabled using Dynamically configured SQL Server memory with 6215 MB minimum memory and 6656 maximum memory settings.
I have now installed, side-by-side, SQL Server 2005 Enterprise Edition in a separate named instance. Everything is running fine but I believe SQL Server2005 could run faster and need to ensure I am giving it plenty of resources. I realize AWE is not needed with SQL Server 2005 and I have seen suggestions to grant the SQL Server account the 'lock pages in memory' rights. This box only runs the SQL 2000 and SQL 2005 server databases and I would like to ensure, if possible, that each is splitting the available memory equally, at least until we can retire SQL Server 2000 next year. Any suggestions?
I tried creating an alias to the server to get it to connect to analyze the server but it will not recognize the SQL 2000 server as a valid server to analyze. I can use the alias to connect in EM or SSMS. Any ideas? The server is not clustered and is at SP4. I've connected to several others in my environment but this one is causing me grief!
I upgraded my SQL 2005 Workgroup 2005 to SP2 and subsequently could not get the SQL Server service running. Turns out this was a problem because I had created separate folders for my data and log files. The distmdl.mdf and mssqlsystemresource.mdf files were in my data folder and distmdl.ldf and mssqlsystemresource.ldf were in my log folder. During SP2 upgrade a new distmdl.ldf and mssqlsystemresource.ldf were created in my data folder. I deleted the distmdl.ldf and mssqlsystemresource.ldf files in my log folder and then moved the newly created ones in my data folder into the log folder and all is well now.
If there was a view that joined 2 tables and I accessed the view the 2 ID fields in the view would still have the AutoIncrement attribute still set to true so that I knew those were Identity fields.
In SQL server 2005
I dont' know why but if you reference a View that has Identiy AutoInc fields in ADO it doesn't keep those properties.
Also for whatever reason we Set the ID field to 0 to let ourselves know its a new Record. SQL 2000 let it happen and assumed it to be null where as By Setting the ID to 0 in SQL 2005 causes it to blow up on me.
Is there some sort of setting in SQL that can make SQL 2005 work like SQL 2000 in these two instances...
Hi, I am having a problem connecting my .net applications from the application server to the database server. When I run the application from my windows xp (sp2) box it works fine. When I try to connect via SQL Management Studio to the database server from the application server I get the same error. Here is the error: System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) Here is the Environment: App Server: Windows Server 2003 Standard Edition Inside Company's Firewall/ Network Database Server: Windows Server 2000 Advanced Edition SQL Server 2000 SP4 Remote Connections to the Server is checked Enable Protocols: Named Pipes & TCP/IP TCP/IP Port: 1402 (I don't know why it isn't the default of 1433) The db server is sitting out side the Company's firewall (don't ask me why). I can access it fine from inside the firewall on my XP box but not from windows server 2003. There is a web server outside the our network that also connects to the db server with no problem and that is running Windows Server 2003 Web Edition. I can ping the db server from the app server using the IP address. I tried using the IP address and the port 1402 in my connection string but that didn't work from any machine (XP and Server). I imagine the issue is somehow related to the company's firewall but why would it only block Windows Server 2003 and not XP? What do I tell the network admin to change? Any help would be appreciated. Thanks, Oran
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.
Currently running SQL Server 6.0 with NT4.0 1]Is it possible to upgrade from 6.0 directly to 7.0? How. 2]I have one database with SQL Server 6.0 on my Production Box & I have another Development box running SQL server 7.0. I want to upgrade my 6.0 database(ON ONE SERVER A) to 7.0 Database(ON DIFFERENT SERVER B) runnung on development box.(I donot want to run Object transfer as The database are quite big & object transfer takes for ever) I want to transfer database and also NT Logins & SQL Server Logins/users.
Hi, I am a Sql server DBA. My new company planning to UPGRADE from AS/400 (DB2) to Sql Server 2000/sql 7.0. Can any one suggest me how i have to plan the upgradation from as/400 to sql server 2000/sql 7.0. suggest me some books , white papers or technical papers. Any suggestions how to convert as400 files to sql server tables.
Hi at here i have a question regarding upgrade SQL server 6.5 To 7.0. Currently , i have a production system running in VB 6.0 with 6.5 SQL server. If i plan for running in 7.0 , is it any impact with my VB coding ? Can i move directly ? Thank !
We currently have a stand alone production server SQL 2005 STD + SP2 and plan to upgrade to clustered SQL 2005 Ent + SP2. What's the proper way to upgrade ? I want the existing server instance use Ent engine.
