• State Verified Answer
  • Replies 4 replies
  • Subscribers 95 subscribers
  • Views 941 views
  • Users 0 members are here
Options
Related

SystemDebugger won't start

haaf
over 1 year ago

I upgraded One Identity from 8.2.0 to 8.2.1.  After installing the new Workstation on my Windows 2016 machine, the SystemDebugger does not want to run anymore.  I start Visual Studio 2017 and load the SystemLibrary.  After logging in, I get the message "The system library assembly was not found.".   I tried reloading the scripts, performing a Clean and a full Rebuild. 

No matter what I do, it just keeps saying "The system library assembly was not found.".   What is it looking for and where??

I've  been developing for many years on this machine, and never had any problems until after the upgrade.

Parents
  • +1 over 1 year ago

    Hello Richard,

    I had the same issue after upgrading from 8.1.4. to 9.1
    Make a copy of the 'SystemLibrary' dir.
    Delete all files and folders in the 'SystemLibrary' dir.
    Run the OneIM autorun.exe install the software in a temp or new directory  C:\temp\One Identity Manager
    Now copy the content of C:\temp\One Identity Manager\SystemLibrary to your actual working directory.
    Maybe this will work for you to.

Reply
  • +1 over 1 year ago

    Hello Richard,

    I had the same issue after upgrading from 8.1.4. to 9.1
    Make a copy of the 'SystemLibrary' dir.
    Delete all files and folders in the 'SystemLibrary' dir.
    Run the OneIM autorun.exe install the software in a temp or new directory  C:\temp\One Identity Manager
    Now copy the content of C:\temp\One Identity Manager\SystemLibrary to your actual working directory.
    Maybe this will work for you to.

Children
  • 0 over 1 year ago in reply to Niels de Groot

    Hi Niels,

    Can't understand or explain it, but your suggestion did work.

    It sounded like the fix I've used in the past ... just copy the SystemLibrary directory over from another machine.  I tried this, and it didn't help.  So, I thought perhaps doing an install to a TEMP dir might do something with assemblies outside the OneIdentity directory, so I installed the workstation in a TEMP dir, and this did not help.  So, I followed your suggestion and cleared out my "bad" SystemLibrary directory, and copied the freshly installed one there.  I noticed that the "bad" directory contained thousands of files, while the fresh one only had a few ".vb" files.  I started the debugger and loaded the files from the DB.  After this, nothing would compile until I added "System.Runtime.Serialization" to the project references.  After this, it compiled and ran just fine.   No clue what your procedure fixed, but I have a running environment again.  Much Thanks.

    ---Richard