Windows Installer problem (?) -- how to debug?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've made several attempts to install an app (BackupExec), all of which end
in an error of "Error 1335: The cabinet file (filename) required for this
installation is corrupt...". I've tried different media and different file
sets, and so ruled-out actual corruption. I suspect something is going awry
in Windows Installer (btw, its a Win 2003 server -- I couldn't find forum
specifically for Windows 200*3* Installer).

Info that might be associated is and "FDI Server Erro".

The problem is this -- I'm having trouble finding info & tips on how to
drill-down into this problem to diagnose it. Can you offer any ideas about a
solution, or about sources of help?

Thanks!
Pete
 
Eggy said:
I've made several attempts to install an app (BackupExec), all of which end
in an error of "Error 1335: The cabinet file (filename) required for this
installation is corrupt...". I've tried different media and different file
sets, and so ruled-out actual corruption. I suspect something is going awry
in Windows Installer (btw, its a Win 2003 server -- I couldn't find forum
specifically for Windows 200*3* Installer).

Info that might be associated is and "FDI Server Erro".

The problem is this -- I'm having trouble finding info & tips on how to
drill-down into this problem to diagnose it. Can you offer any ideas about a
solution, or about sources of help?
Click to expand...

What does Event Viewer say after it fails? (Application log).
 
Graham,

Thanks. I don't have the info on-hand at the moment, but will check it next
time I can get to the server. "Please stand by"...

Pete
 
Graham,

While I'm working to gather Event Log info, here is other, similar (maybe?)
info -- an excerpt from BackupExec's installation log file. I'm puzzled
about why it's installing components for languages (ITA, KOR, JPN) other than
English as I selected by prompts during the install procedure, and about why
it's installing Win98/ME components, and have inquired of Symantec about it.
The error/corrupt message within the BackupExec log are generated, I think,
by Windows Installer.

Hopefully this info will trigger some ideas -- please let me know. I'll
follow-up with actual Event Log info within a few days.

Thanks again for your help
Pete

04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\ITA\VERITAS Backup Exec Agent for Windows 98 and Me.msi
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\ITA\Data.Cab
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\ITA\setup.exe
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\ITA\instmsia.exe
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\ITA\setup.ini
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\KOR\Data.Cab
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\JPN\VERITAS Backup Exec Agent for Windows 98 and Me.msi
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\JPN\Data.Cab
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\JPN\setup.exe
04-11-2006,13:54:54 : C:\Program Files\VERITAS\Backup
Exec\NT\Agents\Win9x\JPN\instmsia.exe
04-11-2006,13:54:55 : ERROR: Error 1335.The cabinet file 'Data.Cab'
required for this installation is corrupt and cannot be used. This could
indicate a network error, an error reading from the CD-ROM, or a problem with
this package.

04-11-2006,13:58:28 : DEBUG: Error 2350: FDI Server Error

04-11-2006,13:58:28 : ERROR: Internal Error 2350.
04-11-2006,13:58:31 : Action ended 13:58:31: InstallFinalize. Return value 3.
04-11-2006,13:58:31 : Action 13:58:31: Rollback. Rolling back action:
04-11-2006,13:58:31 : Copying new files
04-11-2006,13:58:31 : Moving files
04-11-2006,13:58:31 : Creating folders
04-11-2006,13:58:32 : Removing ODBC components
04-11-2006,13:58:32 : Deleting services
04-11-2006,13:58:32 : Stopping services
04-11-2006,13:58:32 : Stopping Backup Exec services
04-11-2006,13:58:32 : RB_StopBEServices
 
All,

Attached are events occurring during the install attempt (sorry about poor
formatting...):
Type Date Time Source Category Event User Computer
Warning 5/3/2006 12:18:22 PM MsiInstaller None 1001 Administrator ACME-SERVER
Error 5/3/2006 12:18:18 PM MsiInstaller None 10005 Administrator ACME-SERVER
Error 5/3/2006 12:18:17 PM MsiInstaller None 11335 Administrator ACME-SERVER
Error 5/3/2006 12:18:11 PM MsiInstaller None 11335 Administrator ACME-SERVER
Warning 5/3/2006 12:17:29 PM MsiInstaller None 1015 Administrator ACME-SERVER
Information 5/3/2006 12:17:28
PM MsiInstaller None 11708 Administrator ACME-SERVER
Information 5/3/2006 12:17:12
PM MsiInstaller None 11707 Administrator ACME-SERVER
Information 5/3/2006 12:15:46
PM MSSQLSERVER (2) 17055 Administrator ACME-SERVER
Warning 5/3/2006 12:15:42 PM MsiInstaller None 1015 Administrator ACME-SERVER
 
Eggy said:
All,

Attached are events occurring during the install attempt (sorry about poor
formatting...):
Type Date Time Source Category Event User Computer
Warning 5/3/2006 12:18:22 PM MsiInstaller None 1001 Administrator ACME-SERVER
Error 5/3/2006 12:18:18 PM MsiInstaller None 10005 Administrator ACME-SERVER
Error 5/3/2006 12:18:17 PM MsiInstaller None 11335 Administrator ACME-SERVER
Error 5/3/2006 12:18:11 PM MsiInstaller None 11335 Administrator ACME-SERVER
Warning 5/3/2006 12:17:29 PM MsiInstaller None 1015 Administrator ACME-SERVER
Information 5/3/2006 12:17:28
PM MsiInstaller None 11708 Administrator ACME-SERVER
Information 5/3/2006 12:17:12
PM MsiInstaller None 11707 Administrator ACME-SERVER
Information 5/3/2006 12:15:46
PM MSSQLSERVER (2) 17055 Administrator ACME-SERVER
Warning 5/3/2006 12:15:42 PM MsiInstaller None 1015 Administrator ACME-SERVER
Click to expand...

You'd really need to look inside some of the Error ones and see what it
says. My guess is that it'll be some kind of component missing or some
such.

This will tell you more about which component is failing. You then have
to trace back and see why it is failed, whether it be a file getting
deleted/overwritten etc.
 
Eggy said:
04-11-2006,13:54:55 : ERROR: Error 1335.The cabinet file 'Data.Cab'
required for this installation is corrupt and cannot be used. This could
indicate a network error, an error reading from the CD-ROM, or a problem with
this package.
Click to expand...

Are you able to open the data.cab file manually?
 
Eggy said:
I've made several attempts to install an app (BackupExec), all of which end
in an error of "Error 1335: The cabinet file (filename) required for this
installation is corrupt...". I've tried different media and different file
sets, and so ruled-out actual corruption. I suspect something is going awry
in Windows Installer (btw, its a Win 2003 server -- I couldn't find forum
specifically for Windows 200*3* Installer).

Info that might be associated is and "FDI Server Erro".

The problem is this -- I'm having trouble finding info & tips on how to
drill-down into this problem to diagnose it. Can you offer any ideas about a
solution, or about sources of help?

Thanks!
Pete
Click to expand...
 
Back
Top