[AnX]

marcdw, on 20 April 2013 - 06:03 PM, said:

@tomasz86

Quote

I don't really know what the problem with the SQL Server is.

Yeah, neither do I at this point. I'm also not a programmer so making full sense of the dump is beyond me.

First, a few points about UURollup v11
1) Two versions of process explorer included. Nice.
2) Caused nvidia display driver service to temporarily hang at startup.
3) May have been premature on saying v11 fixed ssl cert issue. It just may be throwing an exception before it even gets to that point.

Anyway, so today I decided to mess around a bit. First I uninstalled Office 2003 so I can get MS Update working again.
[Note to self - either install Office as the last thing I ever do or just fore-go it for Ashampoo/SoftMaker Office 2010 or 2012.
2010 works fine on a stock win2k]

MS Update offered me two patches for .NET and re-offered Rollup 1.

Back to SQL. I uninstalled v11 which caused win2k to reboot before logon prompt appears. Went into safemode and installed Rollup 2.
After restart I installed v10d and went back to sql. So now we're back to the beginning of not being able to create ssl certificate.
Just for the fun of it I decided to add bits and pieces of v11 to v10d to see what happens. With each addition I'd try and reinstall sql server.

The copying of bits was done via a Linux rescue system. The following dlls were added to the system (system32 & dllcache)...

user32 - no go (meaning the same ssl cert issue)
crypt32, cryptui, wintrust - no go
rsaenh - no go
userenv - no go

Following added just for the fun of it...
cryptsXP, credui, wintruXP, xpsp#res files - no go

Given that those files from v11 didn't change anything I then reinstalled all of v11. SQL Server throws an exception.
Hmm, maybe it's the included uxtheme.dll I thought. Nope.
This could be kernel related or anything for that matter.

BTW, an almost identical exception error was found at MS when I was searching last week with a supposed fix being cumulative update 15
for sql server 2005 sp3. Thing is I can't test that because sp3 itself won't finish installing and thus CU15 can't find any instance to update.

I'm finished for this week. I'll resume testing next week on my next days off.

Marc

You should try a different version of SQL server to see if it works or not.

[marcdw]

AnX, on 30 April 2013 - 01:11 AM, said:

You should try a different version of SQL server to see if it works or not.

Yeah. I can either try SQL Server 2000 (is it free?) or just go with SQL CE (doesn't run as service nor has all the
features but then again I probably don't need much anyway).
After my first round of failures I had installed SQL CE anyway.

I doubt Server 2008 would run even with the unofficial updates (requires .NET 3.5, not sure what else).

Marc

[marcdw]

Latest SQL Server 2005 Test

To AnX: I don't think there's another version of MSSQL that I can try. Version 2000 isn't/wasn't available in an Express edition
as far as I know.
Okay,
Starting from scratch this time.

1) Installed Win2K, SP4, Rollup 1
2) Installed IE6 and essentials (Windows Update Agent, MSI, BITS, and roots update v010)

At this point MSUpdate worked great and I let it do all the patching and updating. Only non-MS addition was to fix
timezone/DST stuff. Everything went smoothly.
Full backup image done.

3) Installed Visual Studio C++ 2005 Express with SQL Server. No problems or errors in Event Viewer.
Though I have an archive of services packs and updates I let MS do it all so I know there's no user error.
4) Service packs, patches, updates to .NET 2, VC++, SQL (SP3 offered).
SP3 failed a few times 'til I found out my MDAC needed updating. After that the SQL update went fine.

In between all this I kept checking and SQL ran without issue. Self-signed certificate was generated and used.
I held out on updating the roots via MSUpdate until I was sure all was working. Updated roots and all was still good.
Another image made.

As a test I took the roots bits from Rollup2 and manually 'updroot'ed them as per inf files. Still all was good.

5) Installed Update Rollup 2. SQL still working with no issues, errors, or warnings.
6) Jumped straight to UURollup v11. SQL throws exception. MSUpdate stopped working. Something about
wuaueng.dll version or database mismatch. Strange since far as I can tell that dll isn't part of the updates.

7) Uninstalled v11. Went smoothly. SQL is working again.
8) Installed UURollup v10d. SQL won't start due to certificate issue...
"...server could not load the certificate it needs to initiate an SSL connection... [error 0x90090008]"
9) Fixed MSUpdate by reinstalling BITS. Was offered up the roots update again.

So, after all this I have learned what? Nada. Nichts. Still where I started.
As mentioned before as a Joe User I really have no need for an SQL server but the fight to make it work has wasted
a lot of days and nights.
Wouldn't have it any other way.

Marc

This post has been edited by marcdw: 05 May 2013 - 06:19 PM

[marcdw]

Two More SQL Tests

Test 1

I thought I was done with this SQL thing but I thought there was some hope.
After giving up on SQL and restoring the main image I installed UR2 and UURollup v11 w20130323.
With v11 running I get the nvidia service temporary hang but in event viewer I noticed a number of errors
regarding WMI and ASP.NET and .NET. I remembered that I had .NET 2.0 SP2 on hand so I installed
that. It fixes the WMI errors.
MSUpdate, after installing the initial .NET2, only offers updates to SP1. Anyway MSUpdate then offered
patches to SP2 along with Rollup 1 (7.7MB).
Also installed KB971111 (.NET GDIPLUS patch) which isn't offered.

There's no SQL installed so I figured I start with the RTM (no service pack). Much to my surprise it did
install with no certificate errors or exceptions. However, sqlserver runs at 99% CPU hogging everything.
This also happened some months ago on another older machine I was testing before.
Tried to use MSUpdate to go to SP3 but the cpu issue was dragging things along. I would periodically
stop the service to give the install a boost but it still was taking forever. Decided to cancel the install which
also took forever.
Installed SP3 from archive instead but once again the server throws an exception.

End test.

Test 2 - and a new daily?

With the RTM version of SQL not crashing I thought there was hope.
This time I restored the image with the working SQL.
Installed .NET2 SP2
MSUpdate offers roots update
Install Update Rollup 2 (SQL running great).
Install SQL SP4 (no probs)
MSUpdate offers roots again (seems to do that a lot)
Install UURollup v10d (SQL certificate problem)

Discovered that there was a new daily available, from April 27.
Installed UURollup v11-d20130427
On reboot I'd get to the logon screen and then error. Services.exe terminated unexpectedly. It reboots. Errors again.
Safe Mode: Uninstall new 11 daily, reboot
Install v11-d20130323 (sql exception, nvidia, MSUpdate broken).
Fix MSUpdate (offered small Rollup 1 and roots)
Safe Mode: Uninstall v11
Safe Mode: Uninstall v10d
Back to normal, SQL is running fine
Safe Mode: Reinstall new v11 daily (in case something got missed)
Boot is successful. Clear logs and reboot just to be sure.
But same as before. SQL throws exception and temporary nvidia service hang.


So there you have it. SQL is definitely, officially out.

Regarding the new UURollup daily, I haven't seen any announcements or what the changes are.
Comparing file dates the only diffs I see is with update.inf and update.ver. Everything else seems the same.

Marc

This post has been edited by marcdw: 08 May 2013 - 04:06 AM