Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
acollins74
Yak Posting Veteran
82 Posts |
 Posted - 2008-07-28 : 14:51:01
|
| KB Number: KB949095Machine: XXXXXXXXXOS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)Package Language: 1033 (ENU)Package Platform: x64Package SP Level: 2Package Version: 3239MSSQL Server 2005 64bit EEI see lots of blogs regarding this similar issue with all kinds of 'try this' fixes. Mostly regarding reinstalling which I find to be a curious solution.But to my point. Cumulative update worked for all instances on an active/passive cluster as well as tools, notification srvcs, integration srvcs on the passive node. Just failed on the Primary Node. On primary node drilling into HotFix logs. Errors stating...SOURCEMGMT: Trying source j:\4703c2fb5ebebc8208aa5822c4bfac53\HotFixNS\Files\.j:\4703c2fb5ebebc8208aa5822c4bfac53\HotFixNS\Files\sqlrun_ns.msp 3: -2147287037 SOURCEMGMT: Source is invalid due to missing/inaccessible package.My question is, what will happen if i create that folder and copy an associated sqlrun_ns.msp into it and give it another attempt. Keeping in mind this is a production system. But not really sure how I can build a test environment b/c all other instances had hotfixes that worked w/o any problems. |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-28 : 22:53:26
|
| Did you put installation package on local disk of the machine? |
 |
|
|
acollins74
Yak Posting Veteran
82 Posts |
Posted - 2008-07-29 : 07:35:55
|
| Yes, All binaries are local to the drive and no installation files have moved from original locations. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-29 : 23:17:31
|
| So j:\ is local disk on the machine? Looks like installation can't open certain files. |
|
|
|
acollins74
Yak Posting Veteran
82 Posts |
Posted - 2008-07-30 : 08:46:32
|
| J:\ drive is on the san. Box has local drives of C and D.All binaries are local to the D drive.Each instance installed on the box has it's own drive(s).For some reason the installation is looking to a folder that does not exist on the J:\ Drive. I have a ton of research and there doesn't seem to be a clear fix but the problem seems to be quite common. My intuition sez, create the file and folder the installion is looking for and all be well. I am just concerned of potential negative impact. I am sure a call to microsoft is in my future. If they tell me anything profound; I'll post it. |
|
|
|
|
|
|
Problems with cumulative update on cluster