SQLX05 SP1 Upgrade To SP2 Acted Like A Failure, But Seems To Work?
Dec 20, 2007
Hi guys, got an interesting scenario: I have a new Dell server with an "empty" Windows Server 2003 SE SP2 installation (all latest updates), joined to a 2003-native domain, ~60 GB/free space, 2 GB ram, P4, etc etc. I loaded up BackupExec 11d 7170, which installs SQL Server 2005 Express Edition SP1.
Before I even used Backup Exec, I knew I wanted to get SQLX05 SP2 installed. First, I followed the preliminary steps listed in the SQL Server 2005 Express Edtion SP2 readme file (backup master/model/msde and bedb/be_dlo databases, verify DB space, verify enabled services/accounts, stop dependant services).
By now it was after-hours and I was away from the office, so I logged into the server with my 2k3 Enterprise Admin account via Remote Desktop. I changed the server from Windows Update to Microsoft Update, and it found/downloaded/installed SQLX05 SP2 for me.
But about 7 minutes later, Microsoft Update told me it failed with code 0x3B30- and the Help & Support had no help for that code.
I started to look around the 'net for the error- I found that some people went into Add/Remove programs, clicked Change on SQLX05, selected the instance, and wound up clicking on "complete the suspended install"- unfortunately, it wanted the source for sqlrun_sql.msi, which I didn't have anywhere, so I clicked Cancel.
I looked at the server, and finally found the summary.txt file buried in C:program filesmicrosoft sql server90setup bootstraploghotfix. It showed passing the prereq check, product detection (2047/express), no disqual'd prods, no locked files, and then had this section:
Product Installation Status
Product : Express Database Services (BKUPEXEC)
Product Version (Previous): 2047
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 15152
Error Description : Unable to install Windows Installer MSI file
Then I saw the hotfix.txt file in the same directory, which had at the end:
More digging found the C:program...loghotfixSQL9Express_Hotfix_KB921896_SQLEXPR.EXEFilesSQLSetup0002_BKUP1_SQL.log file- which was 6822 kb large! But there are repeated errors in it that go something like this:
SQL Server Setup has encountered the following problem:
Failed to execute the Transact-SQL statement: EXEC sp_update_user_instance N'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql'
Script file:
The error was: [Microsoft][SQL Native Client][SQL Server]Cannot update user instances. Reason: Cannot start user instance 'D66F74F5-91FF-40' for update. Error code: 0x3c0c.. To continue, correct the problem, and then run SQL Server Setup again.
Error Code: 0x80073b30 (15152)
Windows Error Text: Source File Name: libodbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@HotfixDBEINST@13
Source Line Number: 91
sqlStatement
Originial error was 80073b30 (15152)
on SqlScript
SqlUpgradeScriptHlpr
Error Code: 15152
Now here's the strange part- I saw something on the 'net that suggested rebooting and applying it again. So I rebooted the server, went to Microsoft Update- and it didn't show that I needed the SQLX05 SP2 update. I checked the Application event log, and it showed that during the SQLX05 startup SQLX05 reported version number 9.00.3042.00! I ran a TSQL command (with sqlcmd) and systemproperty('productlevel') came back as SP2.
I finished my TSQL command, and got a popup from Microsoft Error reporting saying some errors happened recently for hotfix.exe. I clicked showdetails, and the p-vals with information were P2=0x3b30, P4=0x3b30, P5=copyengine.cpp@1653 , P7=sql9express. So I sent the report up.
Out of curiousity, I went back to Add/Remove programs, clicked on SQLX05 and "change", selected the instance, next, next, and wound up at the SQL Server Install Wizard. It STILL had a box for me to click on saying "Complete the Suspended Installation"- so I cancelled it.
But everything "looks" fine! Is it? Can I trust it?? Could Sql Server Express have automatically ran the failed sql files after the reboot?
I am trying to do an upgrade in place from SQL Server 2000 SP3a to SQL Server 2005. I am encountering the following error. SQL Server Setup has encountered the following problem:[Microsoft][SQL Native Client][SQL Server] Password validation failed. The password does not meet Windows policy requirements because it is too short...To continue, correct the problem and then SQL Server setup again. I read the other posting and it mentioned that the sa account needs to be changed. I have changed the sa account to meet the passowrd requirements for our system and have changed the following services I could find over to my domain account which I know meets the password restrictions. If I do a new install, everything seems to load correctly. What options do I have to do this upgrade in place?
A client of mine is trying to upgrade their SQL Server box. They are on SQL 2000 now and the new box will be SQL 2000 as well. Before you ask, they don€™t want to go to SQL 2005 for licensing issues (i.e. cost).
The problem I€™m having is that in addition to moving the database they need to add an update field (smalldatetime) with an index. Adding the new field and index to each table is taking around 16 hours on the new box. This client is an online retail shop and they are completely dependant on SQL being up. The have given me a 2-3 hour window to make the move. So how do I get the database moved and updated in 2-3 hours?
This is what I have done so far: Argued for a longer install window. Being down for 16 hours is a no go, not even an option. Restored a copy to the new server, add the new field and index. Created a temp database on the old server and triggers that log the PK any time a change is made to the current prod db. Then use a script to pull the changed data into the new prod. This looked like it was going to work but it when it gets to the larger and more heavily used tables it takes way to long (25+ minutes per table). That shoots the 2-3 hour window.
Next plan is to move the current database to the new box. Then each night update as many of the tables as I can until it€™s complete. I estimate this will take six to eight days. They are not very excited about being down every night for eight days.
So my question to all of you is; have you had to deal with a situation like this before and if so how did you resolve it? If not do you have any ideas as to how I can get the database moved and updated while keeping my client happy? I would be most appreciative of any advice or suggestions you may have.
I tried using Query Notification on my computer at home: * Win XP Pro with all the SPs and hotfixes * SQL 2005 with SP1 qand hotfix
Query Notification worked fine.
Then I tried using it at work:
* Win XP Pro with all the SPs and hotfixes
* SQL 2005 with SP1 qand hotfix
and I see the following error in the SQL server log file and notification does not get to the client app:
---------------------------------------------------------- Date 9/1/2006 10:18:30 AM Log SQL Server (Current - 9/1/2006 10:18:00 AM)
Source spid17s
Message An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'domainmyuser', error code 0x6e. ----------------------------------------------------------
A similar error shows up in the machine's Event Log.
I am sysadmin and full OS admin on both boxes. The difference is that the computer at home is standalone while the one at work is part of a domain.
Hello, I upgraded to Beta 3 and now mail isn`t working(I hate mail!) I found 2 error messages. One when trying to add an operators email id and the other when I try to "test" mail under server properties.
- Unable to start a mail session on the server with this mail profile.
- no mail profile defined.
The account that I am using is used for all our SQL Servers and was working on this server on 6.5 before the upgrade. I have checked the new SQLServerAgent service and it`s using the correct account.
Any help would be appreciated.
And to all you that are off for a long Labor Day weekend...I`m jealous!
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 ...
My instance of SQL Server Developer stopped working after upgrade of OS from Vista to XP. I have also installed SP1 & SP2. Still it is not working. The message that I get when I start SQL Server Management Studio is "The application cannot start."
Upgraded SQL Server 2005 x64 to Service Pack 1 expressly for the purpose of enabling Database Mail from SQL Job, which was a known bug that was listed as fixed in this Service Pack. It still does not work; in fact after installing SP1 on an x86 SQL Server Standard, Database Mail does not work from there now either, although it did prior to the upgrade! I am using Integrated Security.
Error message received: The job succeeded. The Job was invoked by User <name>. The last step to run was step 1 (Select). NOTE: Failed to notify 'Mike Schelstrate' via email.
Message in Error Log: [264] An attempt was made to send an email when no email session has been established.
Send test Email does work on both Servers.
Here is another Error message I found in the SQL Error Logs: [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs). Looks like this may be the root of the problem because it does not exist, I checked. How do I obtain this missing extended stored procedure?
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 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 am using ODBC to connect SQL Server 2000 + SP4 server runnig on Windows 2003 standard edition Server +SP1. But, sporadically my application server connectivity to DB fails and i receive the following error messages
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (WrapperWrite()). [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.) In D:de.cpp 702 Apr 12 2006 20:34:47 [Microsoft][ODBC SQL Server Driver]Communication link failure) In D:de.cpp 702 Apr 12 2006 20:34:47 20071017 08:23:10 TID (00000ff0) Sev (3) Err (0) Msg (Read failure. General SQL error.
Strange thing is that i receive this error only sporadically, Please Please advice !
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.
SQL 2000 -> SQL 2005 upgrade on windows server 2003 ... We've done numerous side by side types of upgrades which have the advantages of being able to migrate things at a slower pace with limited downtime. I have a situation where it seems like it would be the least amount of work to do an in place upgrade involving 22 transactional in-house developed databases and associated in-house developed applications. There's no replication, no DTS packages, nothing I can think of that would complicate the upgrade. I was wondering if there's people out there that have done lots of these and haven't had any problems OR if there have been lots of problems. Anyway, any advice would be appreciated.
Hi, I have copied my first web site to our web server, the web site is secured using AspNetSqlProvider. I have attempted to browse the site from IIS tree and I am redirected to the logon page as expected. The autentitcation is attempted and fails with: 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) The database is in the app_data file, why is it not found? Regards, JoeBo
Whats happens when moving a sql server database to another sql server database and the DTS fails. Does it copy half the data or it doesn't copy any data????
Does anyone have some suggestions as to why my scheduled recurring DTS packages keep failing to run? I can manually execute the package and it works just fine but I don't know why the schedule job fails and there is not enough information in the error log to help me figure out what I have missed. The DTS is copies a CSV file from a different server into an existing table in my Database. The DTS has the following steps Truncate the table, Copy and import the text file into the table and Finally send me an email if it completes the task.
I have the package and the SQL Agent Service accounts set to my NT Account, which has admin rights
declare @exec varchar(128) set @exec = 'bcp [boxNamemysql2k5].adventureWorks.sales.customer format nul -T -n -f c:customer.fmt' --print @exec exec master..xp_cmdshell @exec
gives me:
SQLState = 08001, NativeError = 17 Error = [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. SQLState = 01000, NativeError = 2 Warning = [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()). NULL
(5 row(s) affected)
It's my local PC, that I am local admin on. I did the same thing (different DB of course) on a local 2000 instance and got the same result. It's been a few years since I used BCP, and this isn't ringing a bell. Can someone please assist?
Dear AllA quick question:I run a set of scheduled jobs. The jobs run Stored Procedures.However, if the sproc fails, the job quits and moves on to the nextone. However, the sproc should carry on. E.g, IF find bad records,EXPORT to file, GO TO NEXT RECORD (BUT DON'T QUIT THE SPROC). The jobscheduler does not allow this, therefore, the sproc does not get achance to finish.Is there a way to ensure a sproc can finish before moving on to thenext step?ThanksSimon
Hi All,We have SQL Server 2000 (sp3), running on Win2k Server. Yesterday, midmorning, during normal processing (selecting data .. loading data ..etc) the sql server service suddenly shut down and would not startagain. We received several messages but the 2 most consistent messageswere that 1) the ums.dll could not be loaded and 2) the services failedto start in a timely fashion.IN the event log, the only thing of interest was this:Application popup: sqlservr.exe - Entry Point Not Found : The procedureentry point?FindNextAvailable@UmsSchedulerQueue@@QAEPAVUmsSch eduler@@W4UmsSchedulerAlgorithms@@@Z could not be located in the dynamic link library UMS.DLL.I am at a complete loss. I did create a new instance of sql Server andreattached all of my databases to the new instance - but, of course, nowthe question being posed to me is "what happened?" I have no idea andam wondering if anyone has experienced this before or has any insightthey might be able to share.Any information would be greatly appreciated! Thanks!Bethany HollidayIU, KSOBIndiana Business Research Center*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
This error continues to occur even after a couple of uninstalls and re-installs, only to result in the same error. I can send the logs if you like, but they are large, so this is the short popup I am getting: ( I can't paste the message, but here is the text:
The installer has encountered an unexpected error: The error code is 2331. Error loading library Cprogram filesmicrosoft SQL Server ... sqlca.dll or finding entry point. The specified module could not be found.
Here is a better message out of the event log:
Product: Microsoft SQL Server 2005 Notification Services -- Error 2331. The installer has encountered an unexpected error. The error code is 2331. Error loading library C:Program FilesMicrosoft SQL Server90Setup BootstrapBin{37E9AD9F-3217-4229-B5A5-7A0C82364C6C}sqlca.dll or finding entry point The specified module could not be found.
Any help would be appreciated. Also, XP Pro SP2. Fresh install, no betas, clean box, not upgrade. Thanks in advance for ANY help! Rick
i am using the ftp task to ftp files from remote location to my local system but the task failed giving error "password was not allowed" (i am trying to retrieve the information for the task from configuration table).pls suggest
I have designed an SSIS that needs to download a set of files via ftp. The ftp is working fine under Business Studio. When I move it to The server and try runing the package I'm getting the following errors:
Error: Unable to connect to FTP server using "FTP Server" Error: An error occurred in the requested FTP operation. Detailed error description: The password was not allowed.
This is not my first FTP in SSIS, so I also have the following item set:
Protectionlevel = EncryptProtectedWithPassword I have several other FTP packages that go to the exact same server, with the exact same user ID and password that are working.
I am new to asp.net 2.0, although I have some experience with asp.net 1.1. In my new machine I have VS 2005, SQL Server 2000 and Sql Server 2005 installed. I wanted to connect to a database in SqlServer 2000 from a simple asp.net 2.0 project. I used the following connection string: string strConn = "Data Source=xyz/abc;Initial Catalog=dbname;UID=abc;PWD=efg;"; xyz/abc is the name displyed in the enterprise manager, under SQLServer Group. When I run the app, I am getting the following error: 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) The error indicates that it is trying to connect to SQL Server 2005, although my xyz/abc is a SqlServer 2000 instance. Not sure how to force the connection to the SqlServer 2000 database. Thanks
Hello Everyone and thanks for your help in advance. I have set up a new installation of SQL Server 2005 and VS 2005. I am trying to get some web applications up and working, but am experiencing problems with the database connection. I am tring to use the the sa account to connect, but am receiving the error "Login for user 'sa' failed. Not associated with at trusted account...". I am familiar with this error and have made sure that the SQL Server is using SQL Server and Windows Authentication Mode. The connection string I am passing to it is: server=(local);uid=sa;pwd=password;database=Northwind which I believe is correct. So I'm confused as to what the problem is. Any help on this topic would be greatly appreciated. Thanks.
I have designed a DTS Package and it can be run successfully from Enterprise Manager. However, when I schedule the DTS package to run as a job then it fails with an error message of "Error string: The system cannot find the file specified.".
Anyone any idea as to why the job cannot find the DTS package?
Can it be something to do with SQL Server 7 and 2000 tools as 2000 Client tools have recently been installed onto my PC and the package and job ran fine when I had designed everything in SQL Server 7.
