Ps4 Pkg Repackager
Mandy Geise
TL:DR - I am having problems with the IS repackager creating an ISR file that it cannot parse to create an MSI from (and, I think, further inconsistencies after I manually edit the ISR file)
I am using IS 2012 Spring Pro v19 SP1. I have used this sucessfully to snap 32 bit apps on a win7 32 bit machine (Running the repackger from an XP SP3 machine where it is installed). Today, I snapped an app for our call centre (Genesys CCPulse+). It is a legacy IS setup program and I could not launch setup.exe with -s -f1"", simply getting an error that setup.exe could not be launched. (Setup.exe needs compatibility mode set to Windows server 2003 to install but otherwise this command line works and the aapplication works when it is installed in this way). I retried letting the repackager run setup.exe interactively and completed the install. The repackager completed its analysis and presented a plausible looking snap although there were a lot of registry keys that didn't seem to have any values in them. I tidied the snap up and attempted to build the MSI. This failed almost immediately with "Unrecognized line in .nir file." in the build log. I repeated the process (I am snapping on a VM which I reset) and got the same result.
This forum post ( -Repackager-building-and-ISM-Problem) pointed me towards Updated.isr (the only ISR or NIR file I had) which I found contained entries such as the following:
[CODE]REGEDIT4
[HKEY_CLASSES_ROOT\CFGSERVER.CfgClientCtrl.1],0,,
""="CfgClient Control"
@=""[/CODE]
...The entry above should be just the default value set to CfgClient Control
[CODE][HKEY_CLASSES_ROOT\CLSID\29C9A70B-5B37-11CF-B546-0000E80C21F3\Control],0,,
@=""[/CODE]
...where there is only a blank, default value (above), it seems to be handled ok
[CODE][HKEY_CLASSES_ROOT\CLSID\29C9A70B-5B37-11CF-B546-0000E80C21F3\InprocServer32],0,,
""="[GENESYS_COMMON_COMPONENTS]dbserver.ocx"
"ThreadingModel"="Apartment"[/CODE]
This entry should be the default value set to the path to the OCX file and a value named ThreadingModel
I edited all of the entries to ensure that they were in the form "value"="data" or @="data" (or @="") and retried building the MSI. This failed again but got much further. There were a number of warnings and errors and I am unsure whether these represent genuine problems with the snapshot or if there are further incompatibilities which mean that the build processs simply cannot interpret it correctly.
For example (from build log)
[CODE]Undefined typelib '29C9A713-5B37-11CF-B546-0000E80C21F3': no component exists for file '[\[]GENESYS_COMMON_COMPONENTS[\]]dbserver.ocx'. This may result in ICE33 warnings.[/CODE]
This file does exist in the snap and appears to have all of the Class definitions in the registry. I note the strange escaping going on around the square brakets for the directory property [GENESYS_COMMON_COMPONENTS]. Could the build process be choking in a similar way to the initial ISR file format issues?
The first path above exists in the snap but has been marked excluded.
The second is where setup.exe is but it is not listed in the files and folders in the snap.
There are subfolder underneath [ProgramFilesFolder] (other than [INSTALLDIR] but nother in c:\ or c:\Program files themselves.
Finally:
Loading File table
[CODE]ISDEV : error -6103: Could not find file "\\swk872\c$\installshield 2012 spring projects\ccpulseplus\[ProgramFilesFolder]\InstallShield Installation Information\EACAB488-C0EA-438B-AC6F-9DDDCB406945\genesys.ico"
ISDEV : error -6103: Could not find file "\\swk872\c$\installshield 2012 spring projects\ccpulseplus\[ProgramFilesFolder]\InstallShield Installation Information\EACAB488-C0EA-438B-AC6F-9DDDCB406945\genesys_ip.ico"
ISDEV : error -6103: Could not find file "\\swk872\c$\installshield 2012 spring projects\ccpulseplus\[ProgramFilesFolder]\InstallShield Installation Information\EACAB488-C0EA-438B-AC6F-9DDDCB406945\internal_uninst.iss"[/CODE]
The same files are referenced WRT MsiFileHash table and creation of.cab files. They are all referenced in the snapshot but have been excluded along with other files in the same folder which do not appear in the log. When I check in \[ProgramFilesFolder]\InstallShield Installation Information\EACAB488-C0EA-438B-AC6F-9DDDCB406945 I find that the three files in the error are absent (other files are present, although the whole folder has been marked excluded). When I search the snapshot folder I find that they are in \[Support]Language Independent OS Independent Files. There are additional files from the application in this folder which are not referenced in the repackger user interface.
Subsequently I copied the three files into the folder that they are listed as missing from and the build now reports that it completes although all of the other class definition registry warnings occur and it doesn't actually create an MSI file where it says it has:
This file doesn't exist although there is an ISM file in there.
I am going to try agin with a basic snapshot rather than installation monitoring... Any ideas gratefully received.
Attached is a zip containing the two build.logs referenced above plus the ISR reg file (before and after editing) and the project INC file
As far as I am aware, the installshield installation on my XP machine (where the repackager is running from) has not be modified since the last successful snap.
Today, more than ever before, it is easier for consumers to reach for their computer, Smartphone or tablet before making purchasing decisions. Consumers can (and do) conduct research online to learn about such issues as what is driving up the cost of health care and prescription drugs. Now patients simply peruse the Internet to select healthcare providers, look up information about side effects of brand name and generic drugs and research how pharmaceutical companies across the supply chain deal with quality assurance concerns.
In the next few months, American consumers will again make vital decisions about health care. Many will spend hours online researching primary care doctors and healthcare providers, examining health care insurance policies. From employees to business owners, the rising cost of heath care and prescription drugs has most Americans concerned and interested in learning how costs can be kept under control.
Whether a patient is dispensed medication from a doctor, hospital, pharmacy, rehab or nursing care facility or other institution, the medication may have originally been packaged in large quantities, rather than individual doses. Increased concerns regarding the quality and cost of healthcare as well as concerns about patient safety have ramped up the need for more unit-dose medications.
Many medications are packaged in large quantities by drug manufacturers. In general, a pharmaceutical repackager purchases medications wholesale, often generic drugs, then repackages them into smaller quantities for sale to doctors. Doctors then sell the repackaged drug products in their offices. Repackaged medications are also sold to pharmaceutical distributors, hospitals or other pharmacies.
Commercial repackaging companies repackage drug product preparations for distribution. This can mean that the drug products are for resale to hospitals, distributors or other pharmacies. Repackaging firms that are FDA-registered regularly receive drugs from hospitals and clinics which are then repackaged into unit-dose packages. This facilitates accurate dispensation of doses to patients and is more convenient for healthcare providers. Operating with a higher level of scrutiny, control, security and quality control, regulated repackagers accomplish the same tasks as other facilities but incur more cost. Because of this, regulated repackagers charge accordingly to maintain a level of profitability. Repackagers are regulated in a very similar manner to how the FDA regulates the packaging operations of the original prescription drug manufacturers.Why Repackage Prescription Drugs?Here are some of the primary reasons for repackaging prescription drug products:
- Makes it easier to serve the needs of individual groups of patients who may require smaller doses of drugs than are available commercially
- Decreases medical and dispensation errors
- Cuts down on prep time, increasing efficiency
- Helps increase pharmacy output
- Decreases drug product waste
- Facilitates effective inventory management
- Reduces the availability of drug products to prevent abuse
- Facilitates use of a specific sized container for use with a particular drug dispensation device
- Makes it faster and easier for practitioners
- Companies which purchase medications from a wholesale distributor or manufacturer then specialize in repackaging the drug products into a new package type. This may be into a smaller or larger quantity package or type of package such as from a bottle into blister cards or unit dose packs that can be used in an automated picking machine.
- Contract packager
- Contract repackagers are third party service providers that do not own the drug products but rather only repackage medications as a service to the inventory owner.
- Companies that relabel drug products
- Pharmacies
- Healthcare institutions including private clinics, nursing care facilities
- Healthcare providers
- Hospital and privately-owned pharmacies