About Martin

Martin · ‎Oct 04, 2019

As promised the option is implemented in the 2019 R2 release. Unchecking Check for broken reference constraints indeed gives a huge improvement in loading the tables in the direct editor. However editing in the direct editor is still a bit of a challenge due to the latency when you try to modify data in a bigger project. Turning off the Reference Tracking as well brings the Installshield Editor up to (it's normal) speed.

Martin · ‎Aug 01, 2019

More in general and not especially 2018 SP1/SP2 we got the same behavior. In our case the cause is the UAC (User Account Control) functionality of Windows. Using "Network Locations" instead of "Network Drives" gives us a usable workaround.

Martin · ‎Jul 11, 2019

Which means that it won't be fixed (Service Pack/Update/patched dll/exe), for the current Installshield 2019 Editor? Just turning it off/disabling it is sufficient for me.

Martin · ‎Jul 04, 2019

Great.

Martin · ‎Jul 04, 2019

In addition to the performance improvement it would be really appreciated if it can be disabled as well. I assume that wil result in the biggest improvement.

Martin · ‎Jul 02, 2019

Recently we started using the 2019 edition of AdminStudio which is the first version for us with "Table Record Reference Tracking" in the Direct Editor of the InstallShield. This feature makes using the Direct Editor for larger projects very, very, very (actually unusable) slow. Just an example: Loading the Component table with +/- 12000 rows takes several minutes. The reference tracking data is also loaded when the information isn't showed. So hiding the information isn't sufficient. I can't discover a setting in the Tools->Options menu to disable this function. Can this function be disabled somewhere/somehow?

Martin · ‎Aug 18, 2016

It works in most circumstances: An addition to the beginning or end of the PATH environment variable doesn't result in a crash anymore. However an "in between" addition results in a crash of the repackager. An older version of the repackager displays a warning message: Changes to the PATH statement have been made that can't be detected by the Repackaging Wizard. You have to use the "AppendPath" command and modify the environment variable manually. The older repackager continues after pressing the only available "OK" button in the dialog box. It doesn't crash. Until now (doing this kind of work for several years) I can't remember I've ever seen this dialog box. So it's not an issue for us but it might be for other people.

Martin · ‎Aug 10, 2016

Thanks. We prefer to use the "multiple steps" method and we are looking forward to get the fix.

Martin · ‎Aug 08, 2016

I tried to narrow down the number of files/regkeys to get a testcase and probably found what's causing the crash... An (any?) addition to the path environment variable results in a crashing Repackager. So instead of the number of files it's something else.

Martin · ‎Aug 03, 2016

It doesn't help. It still crashes on Win7 and Win10 on virtual and real PC's. And: It doesn't crash at launch but during the second snapshot stage.

Martin · ‎Aug 02, 2016

The Repackager (15.0.0.694, part of AdminStudio 2016) crashes when creating the second snapshot. (Multiple Steps repackaging method). Repackaging a small product (+/- 66 files) succeeds but a large product (> 4500 files) gives a crash of the repackager. Repackaging the large product with an older version of the Repackager succeeds without issues. I don't exactly know what number of files results in a crash of the repackager. It's somewhere between 66 en 4500. I tried different large products on different platforms (Windows 7, 32 bit and Windows 10, 64 bit) with the standalone repackager installation and the complete AdminStudio 2016 (evaluation) installation but the Repackager keeps crashing. The three required C++ prereq's (2008, 2010 and 2012) are correctly installed. Installation monitoring as snap technology works on the lager products but we prefer to use the "multiple steps" method. Any idea how to solve this?

Martin · ‎Jul 07, 2016

Same issue for me... Seen this issue before using InstallShield 2013 Professional on Windows 10 Enterprise x64. I assumed it was solved by switching to the most recent version of InstallShield. Unfortunately not. It's a clean machine with a fresh Windows 10 installation on it. COM extraction seems to function quite good on Windows 7 x64, it does something on Windows 8.1 x64 and nothing at all on Windows 10 x64. To complete the information: InstallShield 2015 was used on Windows 7 and 10 (as I mentioned before) and InstallShield 2013 on Windows 8. I used the same InstallShield projectfile and performed the operation on the same component. "COM extract at build" and "Extract FOM Data for Key File" both fail. The first one gives an error during the build process. The second one delivers no outputdata. How can this issue be solved?

Martin · ‎Apr 02, 2014

Selecting a group in the Conflict Solver wizard results in a "not responding" Application Manager. The only option is to kill it when it doesn't crash by itself. Conflict Checking against one package functions correctly. But performing a second run (by pressing "Launch Conflict Wizard" again) results in a "not responding" or crashing Application Manager. Log files and a Word document with some screendumps are attached. Background info: The Application Manager database is created by using the bulk import functionality of the 2012 version of Application Manager because bulk import doesn't work with Application Manager 2013. After the bulk import I started the 2013 version to update the database. The supplied credentials for the Database Connection are those of the dbo. Any ideas to solve this issue?

Martin · ‎Aug 26, 2013

Nobody? Is the question or problem description not clear?

Martin · ‎Aug 13, 2013

Is a repair on user logon an option? If so, you can use an Active Setup: http://blogs.msdn.com/b/aruns_blog/archive/2011/11/02/10176957.aspx

Online Status	Offline
Date Last Visited	‎Oct 04, 2019 10:20 AM

Re: Table Record Reference Tracking

Re: Installshield 2018 Project Not Opening

Re: Table Record Reference Tracking

Re: Table Record Reference Tracking

Re: Table Record Reference Tracking

Table Record Reference Tracking

Re: Repackager (15.0.0.694) crashes during second snapshot

Re: Repackager (15.0.0.694) crashes during second snapshot

Re: Repackager (15.0.0.694) crashes during second snapshot

Re: Repackager (15.0.0.694) crashes during second snapshot

Repackager (15.0.0.694) crashes during second snapshot

InstallShield 2015 COM extraction on Windows 10 x64

Application Manager / Conflict Solver 2013: Unable to check conflicts against a group

Re: Repackager 32/64 bit registry keys

Re: Excel plugin trigger repair on execute

Re: Table Record Reference Tracking

Re: Installshield 2018 Project Not Opening

Re: Table Record Reference Tracking

Re: Table Record Reference Tracking

Re: Table Record Reference Tracking

Table Record Reference Tracking

Re: Repackager (15.0.0.694) crashes during second snapshot

Re: Repackager (15.0.0.694) crashes during second snapshot

Re: Repackager (15.0.0.694) crashes during second snapshot

Re: Repackager (15.0.0.694) crashes during second snapshot

Suggested Actions

Suggest an improvement

Open a support case