This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Martin
Level 5
‎Apr 02, 2014 09:10 AM

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

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?
InstallShield.log
ISCMIDE.log
368 KB
AdminStudioHost.log
0 Kudos

This thread has been automatically locked due to inactivity.

To continue the discussion, please start a new thread.
1 Reply
Alpesh
Flexera Alumni
‎Apr 02, 2014 11:37 PM

Hi Martin,

If you look at the AdminStudioHost.log, you will see that there is some issue with the database. It appears that a stored procedure appears to be missing. Please search for that procedure in the sql scripts available in the AdminStudio install location, and try running that script. Check if that helps you or not.

Thanks!
0 Kudos