After days of searching, instaling and code analysis, I found the solution for the problem. After installing the suite with compatibility mode XP SP3, evaluated rights, you need to apply a fix from Microsoft, which could be found here: https://support.microsoft.com/en-us/kb/195353

Now, everything works fine.

Alan,

I watched the file system as you suggested. The installers work fine in this point, all files created on XP are also created on Win 10, not even one file is missing. But it doesn’t solve the problem. Do you have any further ideas? Do I need to install any pre requirements to bring the suite to work? Maybe something is missing?

As I found out, we already buy the source code, but recompiling all controls doesn’t worth the effort. Before we doing this, we remove all controls of the project and never get frustrated with Infragistics controls any more. But this will leave a bad taste for your controls in further decision.

If I understand you right, you can’t tell me (for whatever reason) how the license system works and what is needed to bring it back to work again. I would be glad if we can find a way to the things to work again!

Alan,

I can fully understand your points and there is nothing I want more to not touch this old vb6 stuff anymore, but I have to. Because at the moment I’m unable to develop or deploy the application, which is pretty bad.

As you mentioned in your post before, I installed the suite on an old XP SP3 machine and checked the registry difference. I also reinstalled the suite with compatibility mode (WinXP SP3, Admin rights) on my developer machine. That’s worked pretty good, only two entries are already exist on my machine which different values, don’t know if there matter.

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00000000-0000-0000-C000-000000000046}\OLEViewerIViewerCLSID] -> No value on my machine

@="{7CE551EA-F85C-11CE-9059-080036F12502}"

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020400-0000-0000-C000-000000000046}\OLEViewerIViewerCLSID] -> IDispatch

@="{D2AF7A60-4C42-11CE-B27D-00AA001F73C1}"

I searched through my entire disk for any files, should all be in the install directory or SysWOW64 Node. I register all of them, only this three wouldn’t work: SSPng2.dll, msvcrt.dll, ASYCFILT.DLL. Don’t know if there are needed or not.

 

Is there any special registry key I need or any special license file I can copy over from my old machine? Because the stuff is really old, is there any way to skip license check? We can continue this conversation in a private way if there is a non-public method available.

Is there any kind of full list for all registry keys? Or any limitations for the search? Because searching the whole registry for “infragistics” or “sherdian” and copy all keys will take much time. And I’m even not sure to catch all necessary keys!

Which assemblies to I need to register manually? Only the assemblies in the install folder? Or are they any other assemblies on other paths like Windows, System, System32, SysWOW64?

Hi Alan,

 

I reproduce all steps mention in the post you shared, but doesn’t change a thing.

As far as I understand, there is no problem with a corrupted installation, there is some kind of licensing issue. If you open a Form uses the SSCheck control, the following error is thrown:

 

“Line 171: Cannot load control SSCheck1; license not found.”

 

Is there any license file missing or a registration outstanding? Can I manually relicense the components? Can I copy and old installation and it will work?

By the way, I’m using Windows 10 x64