December 19, 2008 at 1:01 pm
I know. This is when I wish a former co-work I worked with else where was here. I could spend hours searching MS Knowledge Base and find nothing. I'd go to him and tell him what I was looking for and may 10 or 15 minutes later he'd have 3 or 4 KB articles for me to look at. It's an art form, not a science, when it comes to searching for answers. I guess i just don't ask the right questions.
December 19, 2008 at 1:10 pm
This is a shot in the dark but the First think I believe you should do is to make sure you have "windows" patched at the same level in both. Especially take care of msiexec. I am recommending that because of Error Number: 1635
Good Luck
* Noel
December 19, 2008 at 1:13 pm
You can tell that I'm fried and eager for a 2 week vacation. Where do I look to check the patch levels of the OS. As I said, my network guys are a bit unresponsive today.
Is it MyComputer on the servers??
December 19, 2008 at 1:18 pm
Lynn, its a long shot, but I had a windows SP2 install fail because it could not find a .msp file, and that was a permissions issue to the reskit folder. Give your id full control over the reskit folder.
---------------------------------------------------------------------
December 19, 2008 at 1:28 pm
Long shots are worth a try. Heck I'd try a scatter gun if I thought it would help!
I'll give your idea a look at, thanks.
December 19, 2008 at 1:39 pm
This isn't clustered, is it? Saw a few notes about 64-bit cluster install issues.
December 19, 2008 at 1:44 pm
Nope, this isn't a clustered system. Both are stand-alone installs. Both have their own disks as well. Neither of them are connected to our SAN either.
December 19, 2008 at 1:46 pm
noeld (12/19/2008)
This is a shot in the dark but the First think I believe you should do is to make sure you have "windows" patched at the same level in both. Especially take care of msiexec. I am recommending that because of Error Number: 1635Good Luck
noel, I found the msiexec files on both systems and they are the same versions.
Thanks for the idea, but may not be the problem.
still waiting for some one in our network group to break free and try and help as well.
December 19, 2008 at 1:58 pm
george sibbald (12/19/2008)
Lynn, its a long shot, but I had a windows SP2 install fail because it could not find a .msp file, and that was a permissions issue to the reskit folder. Give your id full control over the reskit folder.
I tried searching for this folder. Perhaps I am not looking in the right place, where would I find it? All search found me was a reskit.chm file.
December 19, 2008 at 2:12 pm
Is there a way to run the service pack install from the command line and have it update only a specified instance, either the default or a named instance?
I'm wondering if the problem is the fact that DWDEV01 has 2 instances, default and one named, and DWDEV02 has only a default instance (okay, it is also running the Windows Internal Database as we have WSS installed on it as well, but it didn't show up when installing the service pack).
December 19, 2008 at 2:44 pm
Lynn Pettis (12/19/2008)
george sibbald (12/19/2008)
Lynn, its a long shot, but I had a windows SP2 install fail because it could not find a .msp file, and that was a permissions issue to the reskit folder. Give your id full control over the reskit folder.I tried searching for this folder. Perhaps I am not looking in the right place, where would I find it? All search found me was a reskit.chm file.
Lynn
C:\tools\reskit
---------------------------------------------------------------------
December 19, 2008 at 3:08 pm
There isn't a C:\Tools directory on either server.
December 19, 2008 at 3:53 pm
then I think I was on the wrong track Lynn, it just sounded simialar to an error I had a while back.
sorry.
---------------------------------------------------------------------
December 19, 2008 at 4:04 pm
Not a problem. I appreciate any help that I am getting.
I may be onto something myself right now finally!
Stay Tuned.........
December 19, 2008 at 4:44 pm
Okay, I think I'm onto something, just not sure what or where it is heading.
This is from the Hotfix.log file on DWDEV02 where the install worked:
12/18/2008 19:44:39.656 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log
12/18/2008 19:44:39.656 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
12/18/2008 19:44:39.656 Registry: Cannot read registry key value "Debug", error 2
12/18/2008 19:44:54.843 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
12/18/2008 19:44:54.843 Registry: Cannot read registry key value "Debug", error 0
12/18/2008 19:44:54.843 Copy Engine: Installed file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x64\1033\SqlSupport.msi
12/18/2008 19:44:54.843 Installed target: DWDEV02
12/18/2008 19:44:54.906 Installed instance: Setup Support Files
12/18/2008 19:44:54.906 Installed product: Redist9
12/18/2008 19:44:54.906 Installing product: SQL9
12/18/2008 19:44:54.906 Installing instance: MSSQLSERVER
12/18/2008 19:44:54.906 Installing target: DWDEV02
12/18/2008 19:44:54.906 Stopping service: SQLSERVERAGENT
12/18/2008 19:44:58.937 Stopped service: SQLSERVERAGENT
12/18/2008 19:44:58.937 Stopping service: MSSQLServer
12/18/2008 19:45:02.953 Stopped service: MSSQLServer
12/18/2008 19:45:02.953 Installing file: sqlrun_sql.msp
12/18/2008 19:45:02.953 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
This is from DWDEV01, where it failed:
12/19/2008 15:42:37.109 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
12/19/2008 15:42:37.125 Registry: Cannot open registry key "Software\Policies\Microsoft\Windows\Installer"
12/19/2008 15:43:33.984 MSP returned 1635: This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package.
12/19/2008 15:43:33.984 Registry: Cannot open registry key "Software\Policies\Microsoft\Windows\Installer"
12/19/2008 15:43:33.984 Copy Engine: Error, unable to install MSP file: d:\45cb8e3f1bce096f01c8e50b6a12\HotFixSQL\Files\sqlrun_sql.msp
12/19/2008 15:43:33.984 The following exception occurred: Unable to install Windows Installer MSP file Date: 12/19/2008 15:43:33.984 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
12/19/2008 15:43:34.859 Watson: Param1 = Unknown
12/19/2008 15:43:34.859 Watson: Param2 = 0x663
12/19/2008 15:43:34.859 Watson: Param3 = Unknown
12/19/2008 15:43:34.859 Watson: Param4 = 0x663
12/19/2008 15:43:34.859 Watson: Param5 = copyengine.cpp@807
12/19/2008 15:43:34.859 Watson: Param6 = Unknown
12/19/2008 15:43:34.859 Watson: Param7 = SQL9
12/19/2008 15:43:34.859 Watson: Param8 = Hotfix@
12/19/2008 15:43:34.859 Watson: Param9 = x64
12/19/2008 15:43:34.859 Watson: Param10 = 4035
You will note the difference on the bolded lines above. Now I just need to figure out the why.
This may mean looking through the logs more since I went into regedt32 on both systems and this registry key does not exist normally apparently, so it must be created during the install process. I just need to see if I can find where and see if I can figure out why it failed on one server but worked on the other.
Again, if anyone looking through the logs finds anything, please let me know, and I am still wide open for other ideas and suggestions.
Thank you again for everyones help so far.
Viewing 15 posts - 16 through 30 (of 71 total)
You must be logged in to reply to this topic. Login to reply