PA
Mon Jul 14 00:31:00 PDT 2008
If the behavior started after installing the update(s), it qualifies as "an
update problem" and only MS Support can help you fix it...for free!
Garth H wrote:
> For me, PA Bear, this does not help. It is not now an update problem.
> The
> problem seems to predate the update problem. As reported, the update has
> been installed. But the original defective creation of the SQLExpress
> service will certainly rear its ugly head again. There are too many
> registry entries to cavalierly delete all such references. The SQL Server
> documentation is just too massive to download at short notice (150Meg+?).
> Since in the SQL Server 2005 Surface Area Configurtor when I try help, I
> get
> 'Help file not found', I am operating blind on this one.
>
> Oh well; it may be corrected during my next format system HDD / reinstall
> cycle in 2-3 months!
>
>> Start a free Windows Update support incident request:
>> https://support.microsoft.com/oas/default.aspx?gprid=6527
>>
>> Support for Windows Update:
>>
http://support.microsoft.com/gp/wusupport
>>
>> For home users, no-charge support is available by calling 1-866-PCSAFETY
>> in
>> the United States and in Canada or by contacting your local Microsoft
>> subsidiary. There is no-charge for support calls that are associated
>> with
>> security updates. When you call, clearly state that your problem is
>> related to a Security Update and cite the update's KB number.
>>
>> For more information about how to contact your local Microsoft subsidiary
>> for security update support issues, visit the International Support Web
>> site:
http://support.microsoft.com/common/international.aspx
>>
>> For enterprise customers, support for security updates is available
>> through
>> your usual support contacts.
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-Windows (IE, OE, Security, Shell/User)
>> AumHa VSOP & Admin; DTS-L.net
>>
>> Garth H wrote:
>>> I had the KB948109 error 0x733F problem-- my original SQL Express 2005
>>> SP2
>>> installation must have been defective. Any way it created a service
>>> MSSQL$SQLEXPRESS which would never start because of not authorized for
>>> access errors regardless of what I did to authorize the user.
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> If you have had an aborted install of SQL you may expect this problem.
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> So I uninstalled SQL Express completely and reinstalled.
>>>
>>> However, it still found, but would not accept, the old service
>>> MSSQL$SQLEXPRESS and would only proceed if I specified "Use Default"
>>>
>>> This reinstall then went OK and reinstalled SQL Express creating a new
>>> service MSSQLSERVER.
>>>
>>> Now I applied the downloaded KB948109 as per Tornalca and it applied it
>>> successfully to the new valid service MSSQLSERVER but not to the old
>>> invalid
>>> service MSSQL$ SQLEXPRESS.
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> So, how do I purge the invalid service MSSQL$SQLEXPRESS from my machine?
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~