Well, I finally defeated a package deployment conundrum.

I did the following until I have hit my brickwall:
  • setup.exe /A
  • Installed ISScript8.msi
  • Took the MSI from the Admin install with the files
  • Did msiexec /i setup.exe ISSETUPDRIVEN=1
  • Excuted the software and it comes up...

But, it doesn't go very far because when I hit a certain button in there which calls what I think is the DAO, MDAC, JET, ODBC, and etc (I don't know which one is doing it. I am thinking it is MSJET more than anything), the softare comes up with a message saying:

"Run-time error '3021': Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record."

Well, I checked Perfmon and Filemon and it seems to be a Microsoft Access MDB lockfile thing that is causing problems. I compared the package with a traditional install and it has problems making this lockfile.

So I am wondering if the setup.exe has something inside of it that integrates with all of the MDAC stuff. I am really at a loss. I would love to get this piece of software going.

Also, the MSI doesn't create shortcuts. Will I have to just create a shortcut in my GPO or something?

Maybe to help:
Originally, if I executed the MSI on its own (InstallShield 8), I would get "1:" and that is it.

I have adjusted permissions on all of my folders to make it where there is no issues. I have even done it for the registry keys. This problem is an absolute nighmare and I would just die to see this software deploy like it is supposed to. This damn thing is holding me up and is making me look like a bad performing employee.

Really, all I need to know is how I could get those specific things like ADO and what-not working inside that MSI installer so that the package does not have any problems. I am about ready to give up completely on this. There is no way I am going to manage 30 laptops on an individual basis. Especially when 40% of them are gone.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


create a verbose log and see exactly where it's failing.

perfmon can help, but you shouldn't need it to tell you what the failure point is in the MSI.
Answered 07/07/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
At this point, I really did wish it was something to do with the MSI install. But it isn't sadly.

The software is running, but doesn't "run" like it is supposed to do so.
Answered 07/07/2008 by: rzkesp
Yellow Belt

Please log in to comment
Use ProcMon not PerfMon to monitor what file and registry activity takes place as the application starts. That will show you whether files and/or registry entries are missing or if the account you're using has insufficient rights.

As to shortcuts, check the 'Shortcuts' table. If there isn't one, no shortcut will be created (unless, like some brain-dead vendors, they're created using a Custom Action). If there *is* one, a verbose log will tell you whether or not the CreateShortcuts action was executed or not.

BTW, I presume you meant:

  • Did msiexec /i [path_to_and_name_of_MSI] ISSETUPDRIVEN=1
rather than:
  • Did msiexec /i setup.exe ISSETUPDRIVEN=1
Answered 07/08/2008 by: VBScab
Red Belt

Please log in to comment