June 17, 2010 at 4:01 pm
I am attempting to load the SQL Server 2005 Client Tools on a PC here at work. I've never had a problem with this, but this one PC is causing me problems.
I really could use another set of eyes looking at the log files to determine what may be the problem. I have a couple error codes from the logs, but haven't found a description yet.
Message pump: 1603
Error Code: 2
Any help is welcome as I continue to comb through the files and such.
June 17, 2010 at 4:32 pm
Okay, in one of the logs I found a message indicating that I needed to be an administrator. That's nice, I am an administrator on that PC, so now what based on that one?
Okay, back to digging...
June 17, 2010 at 4:40 pm
Looks like Error Code: 2 my mean that the system cannot find the file specified, but which file?
June 17, 2010 at 4:56 pm
Did you check for a sqlsp.log or something like that in the Windows folder? I think setup logs stuff in there. Or is this from there?
Are you using same media as for other machines?
June 17, 2010 at 10:05 pm
Steve Jones - Editor (6/17/2010)
Did you check for a sqlsp.log or something like that in the Windows folder? I think setup logs stuff in there. Or is this from there?Are you using same media as for other machines?
I'll look for the sqlsp.log fle and see if it helps. All the attached logs are from log directory under the setup directory of the 90 folder in Microsoft SQL Server.
Yes, I am using the same the media as other machines, in fact I successfully installed the client tools on another machine in the same office today.
June 18, 2010 at 8:06 am
Same media should mean it's not corrupted. I'm not sure if that's the log file, but I've seen SQL setup put a log file somewhere in the Windows folder. Usually I install, then sort that folder by date modified, look for something I that looks like a log file.
My guess is that something on this Windows install is different. Maybe it has a corrupted file that doesn't affect operation normally, but is needed by SQL. Hard to say.
Have you uninstalled, cleaned registry, deleted SQL folders, reboot, reinstall?
June 18, 2010 at 8:23 am
From what i can gather....
the install of msxml6 failed.
Looking at its log (SQLSetup0003_AERO70413_MSXML6_1)
I see...
"This package is not supported on this operating system"
The Error 2's look like they are pretty irrelevant to the "real" error.
Does this pc have the latest .Net framework ?
June 18, 2010 at 8:29 am
June 18, 2010 at 8:30 am
Steve Jones - Editor (6/18/2010)
Same media should mean it's not corrupted. I'm not sure if that's the log file, but I've seen SQL setup put a log file somewhere in the Windows folder. Usually I install, then sort that folder by date modified, look for something I that looks like a log file.My guess is that something on this Windows install is different. Maybe it has a corrupted file that doesn't affect operation normally, but is needed by SQL. Hard to say.
Have you uninstalled, cleaned registry, deleted SQL folders, reboot, reinstall?
Just got in to work, haven't had a chance to get back over to this PC yet. I haven't uninstalled, et. al. as of yet, wanted to review the logs to see what I might find (or anyone else as well).
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply