Cannot install Service Pack2 on Windows Server 2003 SBS
Hi,
I have tried several times to install SP2 on a W2K3 SBS box. Each time it goes through the prep until I get a cannot install catalog files error.
I went to the MS KB site and tried all of their suggestions to deal with this problem but I still get the failed to install catalog files error. Has anyone run across this and found something else that might work to get this darn thing to install? I have been doing this manually. I assume that trying it via the MS Update site will of course yield the same result.
Also currently there is Exchange server sp1 on there. Are there any issues with the sp2 install for this on SBS?
Thanks for your input!
I have tried several times to install SP2 on a W2K3 SBS box. Each time it goes through the prep until I get a cannot install catalog files error.
I went to the MS KB site and tried all of their suggestions to deal with this problem but I still get the failed to install catalog files error. Has anyone run across this and found something else that might work to get this darn thing to install? I have been doing this manually. I assume that trying it via the MS Update site will of course yield the same result.
Also currently there is Exchange server sp1 on there. Are there any issues with the sp2 install for this on SBS?
Thanks for your input!
I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci)
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci)
Comments
-
ITdude Member Posts: 1,181 ■■■□□□□□□□Yes, it successfully goes through all the preinstall stuff right up to backing up the registry and then I get that error..I think it needs about 500MB doesn't it?
I have 13GB free space on the C: drive!I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
royal Member Posts: 3,352 ■■■■□□□□□□Try going to the command prompt and typing: setreg 10 FALSE“For success, attitude is equally as important as ability.” - Harry F. Banks
-
ITdude Member Posts: 1,181 ■■■□□□□□□□ok will try that thanks! No, it is not a fresh install in fact it is the old non R2 version. It has been running on this box since 2005....I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
ITdude Member Posts: 1,181 ■■■□□□□□□□royal, it said set reg is not a recognized as internal or external commandI usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
Mishra Member Posts: 2,468 ■■■■□□□□□□I would try to clean the server up some then try to install it again.
Registry cleaner
Page defrag
Service Packs/Updates
Multiple virus platform scanning
Adaware scanning
Because it is small business server, then it probably is in a small business... They sometimes tend to surf the web and different things on their servers. -
ITdude Member Posts: 1,181 ■■■□□□□□□□Thanks Mishra you might have a point there, although I suspect the problem might be deeper than that like certificate related or the like....I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
ITdude Member Posts: 1,181 ■■■□□□□□□□I just looked at the Security Catalog at:%SYSTEMROOT%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\NT5INF.CAT
I looked at the certificate and it said valid from Friday October 18, 2002 through December 18, 2003.
Am I on the right track here or any other ideas?I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
royal Member Posts: 3,352 ■■■■□□□□□□Well, the setreg command I was getting was from:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q281458
The url also discusses nt5inf.cat. I would give this support doc a look.“For success, attitude is equally as important as ability.” - Harry F. Banks -
ITdude Member Posts: 1,181 ■■■□□□□□□□Thanks but that is the support doc I was referring to also. I cannot get the setreg to execute, it cannot find it anywhere..I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
sprkymrk Member Posts: 4,884 ■■■□□□□□□□ITdude wrote:Thanks but that is the support doc I was referring to also. I cannot get the setreg to execute, it cannot find it anywhere..
Regarding that KB article:APPLIES TO
• Microsoft Windows 2000 Advanced Server
• Microsoft Windows 2000 Datacenter Server
• Microsoft Windows 2000 Professional Edition
• Microsoft Windows 2000 ServerAll things are possible, only believe. -
royal Member Posts: 3,352 ■■■■□□□□□□You appear to be correct Mark about it not being supported. I did read some other website and they said the setreg as well as the nt5inf.cat fix should still apply for Server 2003 so I figured it would be worth a shot. From seeing ITdude's comments though, it appears that the setreg apparently isn't supported in Server 2003.“For success, attitude is equally as important as ability.” - Harry F. Banks
-
ITdude Member Posts: 1,181 ■■■□□□□□□□Yup! I saw that too and was starting to think that it wasn't supported in 2003. However, when I did a search about this problem Microsoft pointed me to that article.
Go figure! Now what?I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
royal Member Posts: 3,352 ■■■■□□□□□□Perhaps try a sfc /scannow. I've also heard a repair install will fix the issue. This would mean you would have to do some repatching, but apparently, people have had luck going this route and then being able to install the service pack afterwards. I'll try to think of some other things you can do, however.“For success, attitude is equally as important as ability.” - Harry F. Banks
-
ITdude Member Posts: 1,181 ■■■□□□□□□□Thanks appreciate that! I really would like to update that darn SBS box but MS sure isn't making it easy for me!I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
sprkymrk Member Posts: 4,884 ■■■□□□□□□□Thanks royal - I have a troublesome 2003 server as well that I have been having fits trying to install SP2. I'll give the sfc a try if you say it has worked for others.All things are possible, only believe.
-
ITdude Member Posts: 1,181 ■■■□□□□□□□I tried sfc remotely but it told me that I needed to be an Admin and using the console. I was using the Administrator account at the time!
I still have feeling this is a security/certificate issue but not sure where to go yet from here...I hope that the Exchange Server upgrade is more straightforward...I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
ajs1976 Member Posts: 1,945 ■■■■□□□□□□Are you using remote desktop to access the server? did you use the /console switch?Andy
2020 Goals: 0 of 2 courses complete, 0 of 2 exams complete -
ITdude Member Posts: 1,181 ■■■□□□□□□□Yes, using RDP and thought I used the switch but might have goofed in typing. My phone rang at the time and I got distracted.
I will try it again later when I can access the server...ThanksI usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
ITdude Member Posts: 1,181 ■■■□□□□□□□No luck so far....Any more ideas?I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
ITdude Member Posts: 1,181 ■■■□□□□□□□Anyone : :I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
tech-airman Member Posts: 953ITdude wrote:Anyone : :
ITdude,
Has the SBS 2003 server been registered and/or activated with Microsoft? -
RTmarc Member Posts: 1,082 ■■■□□□□□□□ITdude wrote:I tried sfc remotely but it told me that I needed to be an Admin and using the console. I was using the Administrator account at the time!
I still have feeling this is a security/certificate issue but not sure where to go yet from here...I hope that the Exchange Server upgrade is more straightforward...
Start > Run > mstsc /console
Log in again as your admin account and try the install again. -
sprkymrk Member Posts: 4,884 ■■■□□□□□□□I just figured out why mine wouldn't work. I had to have the Distributed Coordinator Service running. It was disabled on this particular server.
Might be worth checking on yours.All things are possible, only believe. -
ITdude Member Posts: 1,181 ■■■□□□□□□□Okay, I will try both of your suggestions and report back...ThanksI usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
ITdude Member Posts: 1,181 ■■■□□□□□□□Tried both and nether helped. Still fails the installation right after backing up the registry....beats me.. :I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
sprkymrk Member Posts: 4,884 ■■■□□□□□□□Have you seen this article?
http://support.microsoft.com/kb/822798
Lots of things to try we haven't discussed here yet. Not sure if you saw it.All things are possible, only believe. -
ITdude Member Posts: 1,181 ■■■□□□□□□□Yes, I have and tried most if not all with no success....Really great that you cannot even update your server because of something granular! :I usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci) -
ITdude Member Posts: 1,181 ■■■□□□□□□□Still have not had any success with this. Anyone have any possible leads other the going to the source?
ThanksI usually hang out on 224.0.0.10 (FF02::A) and 224.0.0.5 (FF02::5) when I'm in a non-proprietary mood.
__________________________________________
Simplicity is the ultimate sophistication.
(Leonardo da Vinci)