KACE Product Support

I'd recommend doing each software package separately. What I do is i have a virtual machine (we use VMWare ESX but you could use vmware player, for example) that just has windows and appdeploy packager. I take a snapshot of the VM. then i capture the install of the software and create the package, roll back the machine and try my install package.

any time i've tried to install multiple items, like FileMaker and patch, the package failed.

As for building the package, i'm not sure this is the correct way but what works for me is to run the capture using the pre/post shapshots. then you run the repackager again selecting "build package based on recipe file" an use the xml file created by the first pass to build the final version of the msi

this seems like a lot of work but I think it is worth it since after you have the well built msi(s) your end up saving your self tons of work.

Hope this helps.

Matt

ltd2007, this sounds like it might be the same as in another thread, where no CAB file is being created; all you have is a bare-bones MSI missing the actual install data. If you can help us reproduce this we can get it fixed! Are you seeing this with all installers? Where are you saving the MSI to?

Hi,
I am saving the MSI to the default location (c:\program files...).... I was doing some reading on the forum last night and I believe I am having that exact same issue - no cab file is being created...

I am running repackager on Windows XP Professional (clean install ofcourse)... I just tried using the existing recipe file and saving the msi to the root of C:\... Still small file size, and won't install (most likely missing the cab file).

Can you look at c:\ErrorLog.txt and tell us what the last few lines say?

yup.

Recipe File Version = '1.1' AppDeploy Repackager Version = '1.1'
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in FILE_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in COMPONENT_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in FEATURE_COMPONENT_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in FILE_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in COMPONENT_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in FEATURE_COMPONENT_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in FILE_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in COMPONENT_TABLE case
13-Nov-2009 08:38:00 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in FEATURE_COMPONENT_TABLE case
13-Nov-2009 08:38:07 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in REGISTRY_TABLE case
13-Nov-2009 08:38:08 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in REGISTRY_TABLE case
13-Nov-2009 08:38:31 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in REGISTRY_TABLE case
13-Nov-2009 08:39:08 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in REGISTRY_TABLE case
13-Nov-2009 08:39:10 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in REGISTRY_TABLE case
13-Nov-2009 08:39:58 CMSIHandler::PopulateMSITable: Error in function MsiDatabaseOpenViewA in REGISTRY_TABLE case
13-Nov-2009 08:40:30 CMSIHandler::BuildMSI:Unable to set MsiRecordSetStream for C:\MSIProject.cab

LD,
Did you have the same issue with 1.2?

thanks for the response...
I just tried 1.2 and got the same error when it came to building the cab file:

16-Nov-2009 13:13:56 CMSIHandler::BuildMSI:Unable to set MsiRecordSetStream for C:\Program Files\AppDeploy\Repackager\Packages\MSIProject.cab

on the same system, using repackager 1.2 still
I just created a new msi where all it is doing is planting a file on c:\ and it works fine, ran the msi on another workstation, install ssilently and planted the file successfully.

i am also seeing these messages in the log file:

16-Nov-2009 13:17:20 CRegSnapshot::GetSnapShot - RegOpenKeyEx: Access Denied HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Credentials: Error 5:

Thanks for the feedback, we are testing a fix for this internally now and I hope to have a new 1.2 beta with the fix to you very soon.

understanding that the application is freeware , and appreciated, any idea of when that release might be made available?

if not, do you know of a possible work around?

Could you attached the recipe (xml) file for us to have a look?

Hi,

I tried the new beta version posted but am still seeing the same results. In the recipe file I am seeing all of the files and registry keys that appear to be correct.... The MSI still looks to be without a cab though (420 KB)...

Still see the following in the Errorlog :



Recipe File Version = '1.1' AppDeploy Repackager Version = '1.2'
23-Nov-2009 13:38:21 CRegSnapshot::GetSnapShot - RegOpenKeyEx: Access Denied HKEY_CURRENT_USER\Software\Microsoft\Protected Storage System Provider\S-1-5-21-1229272821-1647877149-839522115-500: Error 5:

ltd007, thanks. Regarding the small invalid MSI file, do you have a TEMP environment variable defined?

> CRegSnapshot::GetSnapShot - RegOpenKeyEx: Access Denied

This line in the log can be ignored. It just means your user is unable to read that registry item. It wouldn't be one you'd want included in the MSI anyway.

Hi,
Environment Variables:
TEMP = C:\Windows\TEMP
TMP = C:\WINDOWS\TEMP

any other suggestions?

Would it be possible to attach the recipe file and the MSI?
Hard to give any advice without the source to check.

ltd0007, I sent you some email a couple of days ago. Did you get it? Hopefully it wasn't junked :)

hi there, sorry got caught up in some projects but I'm back on this now... I did get your email, will respond shortly.

thanks for the help again..