Server 2003 - office 2000

[mtevensorrison]

Hello there

recently we had to do a clean install of server 2003 on our appserver.

now before the installation i had office 2000 installed, we use terminal services and i had installed office so clients were not switchin from their own PC's to use certain applications!

Now when i try and install office 2003(which i have stored on the hard drive), i enter the serial number, the installer runs for a minute or so before stooping Rocky.acs and displaying the folliwing error - - - - -error 1335 the cabinet file required for this installation is corrupt

Now ive installed this on client PCs running XP and had no problems at all

Can someone please put me out my misery here!

 

[mtevensorrison]

Correction from the header everyone, its actually office 2003 im attmepting to install!

 

[Roadki11]

Did you put the server in install mode and/or are you trying to install from an RDP session or at console?

 

[58sniper]

Running Office setup will automatically put a TS server in install mode.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[markdmac]

http://office.microsoft.com/en-us/ork2003/HA011402071033.aspx

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[mtevensorrison]

I have not put the server in install Mode, not really sure how to to be honest!

IM also trying to install from the sever itself not an RDC!

 

[mtevensorrison]

Thanks for youre help guys but still no joy!

Im still getting this error

Error 1335: the cabinet file 'CR561401.CAB required for this installation is corrupt and cannot be used this could indicate a netwrok error, an error reading from the CDROM or a problem with this package.

i cant find a solution anywhere, must be a solution somewhere!

Thanks again

p.s, i only have internet access in work so i cant reply at night

 

[58sniper]

Looks like bad installation source.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[mtevensorrison]

But i can install it on all client machines, but not the server!

 

[mtevensorrison]

Still no solution for this and it really had got me scratching my head!

does anyone have any fresh leads!

cheers again

Stevie

 

[Tricky100]

Looked at this?

http://support.microsoft.com/kb/314810

 

[mtevensorrison]

I will try and change the memeory settings on our server!

Does anyone know if this will have any bad effects or if it will go smoothly!

 

[mtevensorrison]

Ive just checked the MAXMEM on the appserver and it is set at 2048!

should this be changed to 256 or will it make any difference!

thanks again

 

[Tricky100]

Without knowing your setup i cant say for definate. your only changing the memory allocation so if your machine is idle most of the day shouldnt cause too many issues. Looks easy enough to change back, but as always changing Reg keys MAY cause issues.

 

[mtevensorrison]

Would the memory stop the installation of office though?

 

[Tricky100]

SYMPTOMS
When you try to install Microsoft Office 2000 or Microsoft Office XP, you may receive the following error message:
Error 1335-Cannot copy cab file Office1.cab. The file may be corrupt.
When you start the computer in Safe Mode and then try to install Office, you may receive the following error message:
The Windows Installer Service could not be accessed. This can occur if you are running Windows in Safe mode or if the Windows Installer is not correctly installed.
You may receive this error message even when the Office CD-ROM package works correctly on another computer.

When you try to install Office while you are logged on to the computer with administrative rights, you receive the same error messages.
Back to the top

CAUSE
This error can be caused by dirty media, CD-ROM read issues, or problems with memory allocation.
Back to the top

be warned its a Similar message not the same one, but matches up as it says you can install on other computers. Have you not got a spare 2003 box you can mess about with in your test environment?

 

[mtevensorrison]

Ive not attempted to install it while in safe mode, i suppose this points to memory allocation or the windows installer!

unfortunately i do not have a spare copy, i have access to the office installation all over our network if you have any test ideas!

this really has me baffled, a brand new server 2003 installation that wont install office 2003, strange

 

[mtevensorrison]

Still no joy with this pain in the neck, changed the memory allocation and still no joy, i know im clutching at straws now but has anyone ever overcame this problem?

 

[Tricky100]

Any event viewer id number for this? and source

 

[kmcferrin]

Have you tried getting a fresh copy of the installation source? It's certainly possible that installing it on a Windows 2003 TS would use different options than it would installing it on a Windows XP workstation, and might require different .CAB files. So if you had a corrupt .CAB file that was required for a 2003 install, but not on an XP install, that would explain your symptoms.