KB948110 fails to install
I keep getting failed updates on KB 948110, and if I download the install manually, and run it, the message pops up as "A Strong SA password is required for security reasons. Please use SAPWD switch t supply the same"... and it exits.. Any one seen this before?
Antworten
- I'm seeing the same error on one of my servers. This particular server has ADMT installed, which is the only application that uses MSDE (both were installed together). I don't know if that's the cause of this particular problem, but it seems to be related. If someone knows if resetting the MSDE SA password won't break ADMT, then I'd like to hear it.
Alle Antworten
- I have seen exactly the same error. (SBS 2K3)
I am seeking further details.
Anon.
ScN - I'm seeing the same error on one of my servers. This particular server has ADMT installed, which is the only application that uses MSDE (both were installed together). I don't know if that's the cause of this particular problem, but it seems to be related. If someone knows if resetting the MSDE SA password won't break ADMT, then I'd like to hear it.
KB948110 - MS08-040: Description of the security update for SQL Server 2000 GDR and MSDE 2000: July 8, 2008 not getting installed on the server.
From command prompt you can try this command. It will work ( Microsoft recommendation).
SQLWMSDE-KB948110-x86-ENU.exe /upgradesp sqlrun INSTANCENAME=UDDI /l*v %windir%WMSDE.log
Thanks,
Biswajit De
- Biswajit, thanks for posting the setup command.
I was able to install the update to patch the ADMT MSDE runtime and received no error messages. My process to install the update was as follows:
- Stop the MSSQL$MS_ADMT service.
- Make a backup of the %windir%\ADMT\MSSQL$MS_ADMT directory.
- Run the KB948110 installer with the command line SQLWMSDE-KB948110-x86-ENU.exe /upgradesp sqlrun INSTANCENAME=MS_ADMT /l*v %windir%\WMSDE.log
- Start the MSSQL$MS_ADMT service.
I just spent 3 hours on the phone with Microsoft tech support to resolve this.
The patch installation uses the SQL SA user, which has sysadmin privileges. If you download and attempt to install the patch manually, you get a dialog box where you are asked to enter the SA password.
My SQL Server 2000 installation is the MSDE version bundled into a commercial product. The developers of the product will not tell the purchasers what the SA password is, and for good reason. Users could do some serious damage to the product's underlying database.
If you don't know the SA password, what can you do?
The manual installation gives you the option of logging on with Windows Authentication instead. It will look in the SQL installation to see if your Windows user ID has SQL sysadmin privileges. My user ID has Windows Administrator privileges, so it is automatically included in the SQL "BUILTIN\Administrators" group. But the developers of the commercial product had removed sysadmin privileges from the SQL "BUILTIN\Administrators" group as another way to protect the database.
The Microsoft rep used the OSQL utility, available even in the MSDE version, to logon to the server with my Windows user ID. The command for that is:
C:\>OSQL -S COMPUTER-NAME\SQL-SERVER-NAME -U WindowsID -P WindowsPassword
Next, we looked for SQL users that had sysadmin privileges:
1> exec sp_helpsrvrolemember 'sysadmin'
2> go
I was very, very lucky that the list returned by this command included another user I recognized as part of the commercial product, AND I knew how to get the password for it. By the way, "exit" is how to get out of the OSQL utility.
We logged back on to the server with OSQL using that SQL user I recognized:
C:\>OSQL -S COMPUTER-NAME\SQL-SERVER-NAME -U SQLUser -P SQLPassword
Now we could give my Windows user ID the sysadmin privilege (the single quotes are required):
1> exec sp_addsrvrolemember 'COMPUTER-NAME\WindowsUser','sysadmin'
2> go
''COMPUTER-NAME\WindowsUser' added to role 'sysadmin'.
Finally, we ran the patch installation again and this time, just clicked Next to accept the default authentication, which is Windows, not SQL. It worked! The patch installed. No special command line switches were necessary; I just typed the name of the file I downloaded.
I didn't want to leave that security window open, so I used OSQL to remove the sysadmin privilege from my Windows user when I was finished (the single quotes are required):
1> exec sp_dropsrvrolemember 'COMPUTER-NAME\WindowsUser','sysadmin'
2> go
I haven't had good experiences with Microsoft support in the past, but this representative did an excellent job. He was located in India, but his English, troubleshooting skills, and product knowledge were refreshingly good. And he used his real name!
Biswakit:
I've tried this method on two different 2003 SP2 servers here today and after rebooting they both still want to see the path installed....doesn't seem to be working here. What am I missing???
I have NO clue what database names might be involved as they were oviously part of a piece of vendor installed software and frankly have no idea how to go about finding them either....not a DBA at all.
HELP!!
George
I saw the same behavior--the patch installed, but the next day, Automatic Updates wanted to install it again. I downloaded and ran the latest version of the Microsoft Baseline Security Analyzer, and it verified that the patch was installed. After I was finished running MBSA, Automatic Updates shut up.
You can use the BLANKSAPWD=1 for the update to ignore a blank sa password.
I have 3 instances of SQL in my SBS 2003 R2 installation (look in services):
MSSQL$SBSMONITORING (currently disabled... I'm not still using it)
MSSQL$SHAREPOINT
MSSQL$WSUS
I stopped the services sharepoint and wsus
I ran the command for WSUS instance from command prompt in the directory where I downloaded the patch
SQLWMSDE-KB948110-x86-ITA.exe /upgradesp sqlrun INSTANCENAME=WSUS /l*v %windir%\WMSDE.log
The installation told me I have another version...
I ran the command for SHAREPOINT instance
SQLWMSDE-KB948110-x86-ITA.exe /upgradesp sqlrun INSTANCENAME=SHAREPOINT /l*v %windir%\WMSDE.log
It finished without errors..... but also without "OK" informational dialog boxes.
Restart my SBS...
The automatic updates show me AGAIN the 2 updates KB948110 to install...
This is also not installing here on two 2003 R2 servers using either method (one has just UDDI as an instance the other has a few oters. On the server with just the UDDI Instance I receive the following in the event log: Obviously its still showing up in needing to be installed, and I've also tried te MSBA 2.1 run as well as suggested by another user as well as a reboot. I've NOT done this on the other machine as its more difficul to take down the main server for the county animal shelter than a test box I can play with.
SQLWMSDE-KB948110-x86-ENU.exe /upgradesp sqlrun INSTANCENAME=UDDI BLANKSAPWD=1 /l*v %windir%WMSDE.log
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11316
Date: 07/14/2008
Time: 06:24:20
User: NETWRX1\Administrator
Computer: APOLLO
Description:
Product: Microsoft SQL Server Desktop Engine (UDDI) -- Error 1316.
A network error occurred while attempting to read from the file: e:\8d5e39cbd4e7cf5614ae106be3a5\Setup\sqlrun.datFor more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 42 34 32 33 33 39 43 {B42339C
0008: 44 2d 39 46 32 32 2d 34 D-9F22-4
0010: 41 36 41 2d 41 30 32 33 A6A-A023
0018: 2d 44 31 32 39 39 30 45 -D12990E
0020: 30 42 39 31 38 7d 0B918}Stefano,
I have SBS 2003 with the same MSDE instances. In my case the update for one instance had been installed; SBSMONITORING. I verified this by running the following T-SQL commands against each instance:
osql -S <servername>\msdeinstance -E
1> SELECT @@VERSION
2> goIf the version is 8.00.2050, the update has been applied.
After stopping all three instance services, I applied the patch to WSUS and SHAREPOINT, restarted the server, and verified the version was as above. Windows Server Update Services still shows the update as not installed even though I forced a resync (wuauclt /resetauthorization /detectnow) however my experiece with Windows Server Update Services dictates I should wait and see.
I believe in your case you will need to also update SBSMONITORING, even though it is disabled, or automatic updates will keep prompting you to do it!
Thanks to the other posters. I found the comments very helpful.
regards
Jon Beets
Well done pcoates, this did it for me. Quite why Microsoft seem to make it so difficult to find the solution is beyond me, however thanks to you I have now solved the problem. Top marks.
- I also have a problem with MsiInstaller while trying to install hp health check update sp39157: Product:HP Active Support Library--Error1316. A network error occurred while attempting to read from the file
c:\Windows\Installer\HP Active Support Library.msi Anybody who can help me resolve this is very much appreciated. Thanks a lot.
- Als Antwort vorgeschlagenSprinter22 Donnerstag, 11. Dezember 2008 16:05
Hi JonBeets,
You just save my day, thanks. For those who may mlike to know, this is what I done;
At the command prompt (DOS screen) type the following
osql -S <servername>\msdeinstance -E
1>exec sp_addsrvrolemember 'domain_name\userlogon_name','sysadmin'
2>go
3> exit
Close the DOS Box.
Logoff and Logon to the server with the above domain user name.
Apply the patch then restart the server.
I did this to 2 WSUS server. The first application was perfect, the seconda update to a different WSUS server completed without error, but WSUS still thinks that the patch not yet applied! Strange! Anybody can shed some light, will be appreciated.
Try the following:
Instead of running the patch directly extract the files to a folder (e.g. C:\SQLPATCH).
Then copy the SQLRUN.DAT from the I386 folder of your Windows Server instalation CD (or DVD) and place it on the
setup folder under the one you have created (e.g. C:\SQLPATCH\Setup)
Now, from a DOS prompt, in the C:\SQLPATCH folder (or what name you have gave it) issue the following command:
setup.exe /upgradesp sqlrun INSTANCENAME=UDDI BLANKSAPWD=1 /l*v %windir%\WMSDE.log
That should do the trick without having to edit the registry or changing sa password.
Hope it helps
Paulo Pinto
PORTUGAL
I had this problem as well. The solution for me was to start the MSSQL$SBSMONITORING service, which was not running. After starting this service, the update installed without issues.
I have the same problem, HP Help did not fix as they asked me to roll back, but that gives an "newer version available"
Thanks.
I'restarted the server and its all good.
Thanks all.
orv
I had the same issue and recieved the following advice from HP
"I understand that you are receiving an Error;- 1603 Fatal error when trying to update HP Active support library.
I will certainly assist you in this regard.
Please be informed that these errors occur when Visual Basic Scripting is not active. To prevent these errors from opening and to install HP Active support library, do the following:
1. Click Start , All Programs , and then Accessories .
2. Right-click Command prompt and select Run as administrator .
3. At the command prompt, type the following and then press Enter :regsvr32 /u vbscript.dll
Note: A success message opens.
NOTE: An error message opens instead of the success message when the command is not entered correctly or when the command prompt window is not an administrative command prompt window. When an error occurs, retype the command text and make sure the text is typed correctly. Also, if the command prompt text is not "C:\Windows\System32", close the command prompt window and repeat these steps (using a login that has administrator rights).
4. Click OK and go back to the command prompt.
5. In the Start Search field, type the following and then press Enter :regsvr32 vbscript.dll
Note: A success message opens.
6. Click OK and close the command prompt window.
7. Install HP Active support library again."Hope this helps
Roger
This worked for me as well. It was a bit odd. This is a brand new server install SBS 2003 R2 no 3rd party anything yet. I was just letting it install the updates.
These forums are GREAT!!
- The solution worked great!
- I managed to install on a WSUS server with
SQLWMSDE-KB948110-x86-ENU.exe SAPWD=XXXXXXXXwhere XXXXXXXX is a "strong" password. A good idea to keep that somewhere in case you ever need it. Thanks aremmes. It worked for me. But now ntbackup fails during a system state backup. With the error below:
Volume shadow copy creation: Attempt 1.
"MSDEWriter" has reported an error 0x800423f4. This is part of System State. The backup cannot continue.Error returned while creating the volume shadow copy:800423f4
Aborting Backup.When I stop the MSSQL$MS_ADMT service and run the backup, it works with no problem.
Has anybody experienced this problem?
After extensive research I have figured out that this problem is caused by Active Directory Migration Tool (ADMT).
Just uninstall the application (you are probably done using it anyway), the update works fine.
Hope this helps,
Emre
Thank you very much, you save my day
This solutions works fine
cheers
I just spent two hours with the same problem.
First I tried changing the SA password to have a stronger password - this did not work
Next I downloaded KB948110 and tried to run the install manually - this did not work either
I finally got the update to install through MS update by doing the following:
Set the MSSQL$SBSMONITORING to manual (was disabled)
Started the MSSQL$SBSMONITORING service
Installed KB948110 through MS update web-site
restarted server
This brings up the syntax window. Something tells me that Microsoft didn't recommend a line with syntax errors?
Not only did this one fail, the downloaded update now reports "the instance name specified is invalid". When I look in HKLM\Software\Microsoft\Microsoft SQL Server\InstalledInstances,"default" says SBSMONITORING.
Why oh why does Microsoft keep getting worse and worse when updating?
Tried this one. It reported back that the product wasn't even installed...(despite the service being running)...
I didn't expect this to make any difference to the KB948110 error - and it didn't. Are you sure you're posting in the right place?
Thank you - helped me !!!
Regards Anders
- Worked like a champ on the SBS 2003.
Thanks - this got the hotfix working on an ADMT machine here. Although I'd been typing "instance" instead of "instancename" which wasted a little time!
- I found the same thing. I started the MSSQL$SBSMONITORING Service manually and the update installed without a problem.
- Als Antwort vorgeschlagenhollidaysjohn Donnerstag, 14. Mai 2009 22:38
Roger,
I tried this to no avail. I did exactly as you said & got the succeeded window, clicked ok, closed the command prompt window & tried to install active support library again. I still keep getting the following window:
HP Active support Library Error
error 1316.A network error occurred while attempting to read from the file
c:\windows\installer\HP Active Support Library.msi
then another window pops up after I close this one & says:
Feature transfer error
error 1603 fatal error during installation
consult windows installer help (msi.chm) or MSDN for more information
I am at my wits end as to what to do about this. Can you or anyone help me. I am pretty much a novice so step by step would be most helpful.
My system is a one year old Hp notebook running windows vista
I downloaded KB948110 and ran manually.
First attempt failed: "C:\Documents and Settings\administrator\Desktop\SQLWMSDE-KB948110-x86-ENU.exe" /upgradesp sqlrun INSTANCENAME=SBSMONITORING /l*v %windir%\WMSDE.log
Changed MSSQL$SBSMONIOTORING service from Disabled to Manual, started it and tried the comand again but it still failed.
Then I tried: "C:\Documents and Settings\administrator\Desktop\SQLWMSDE-KB948110-x86-ENU.exe" /upgradesp sqlrun INSTANCENAME=sharepoint /l*v %windir%\WMSDE.log and it succeeded.
Ran Windows Updates again and it still showed me the update. Selected to install it and this time it completed.
One key in the puzzle is NOT having the MSSQL$SBSMONITORING service disabled!
- iamladynightmare said:
Roger,
I tried this to no avail. I did exactly as you said & got the succeeded window, clicked ok, closed the command prompt window & tried to install active support library again. I still keep getting the following window:
HP Active support Library Error
error 1316.A network error occurred while attempting to read from the file
c:\windows\installer\HP Active Support Library.msi
then another window pops up after I close this one & says:
Feature transfer error
error 1603 fatal error during installation
consult windows installer help (msi.chm) or MSDN for more information
I am at my wits end as to what to do about this. Can you or anyone help me. I am pretty much a novice so step by step would be most helpful.
My system is a one year old Hp notebook running windows vista
- SQLWMSDE-KB948110-x86-ENU.exe
is not a recognized commande - SQLWMSDE-KB948110-x86-ENU.exe
is not a recognized command - SQLWMSDE-KB948110-x86-ENU.exe
is not a recognized command
