This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Registry error for ISUSPM causes System32 to open at startup
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Sep 08, 2010
03:48 PM
Registry error for ISUSPM causes System32 to open at startup
I have created an install shield project that relies on Flexera’s FlexConnect Pro hosted solution. I have included in the project the “Flexnet Connect with Software Manager” merge module.
The problem is that after installing my software on a computer, the computer shows the System32 folder on start up.
I have tracked the cause of the problem down to an incorrect registry entry created during installation. Under the registry path
“HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\” There is a key with the name “ISUSPM” and data set to “-scheduler”.
I believe the data for this key should be
“C:\Documents and Settings\All Users\Application Data\FLEXnet\Connect\11\ISUSPM.exe –scheduler”.
Can you please help me find a way to correct this bug.
The problem is that after installing my software on a computer, the computer shows the System32 folder on start up.
I have tracked the cause of the problem down to an incorrect registry entry created during installation. Under the registry path
“HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\” There is a key with the name “ISUSPM” and data set to “-scheduler”.
I believe the data for this key should be
“C:\Documents and Settings\All Users\Application Data\FLEXnet\Connect\11\ISUSPM.exe –scheduler”.
Can you please help me find a way to correct this bug.
(4) Replies
Oct 29, 2010
03:25 PM
I contacted support and they were able to help me solve this problem. I was using the “FLEXnet Connect with Software Manager” merge module version 11.60. After following their suggestion to include the latest FNC 12.01 merge module which can be selected under the redistributables view in IS2010 or IS2011, I know longer had the problem. As a note, if it is not under the redistributable view you need to update the Flexnet SDK.
Hope this helps you.
Hope this helps you.