Hi,

One of our VC installations has a problem when trying to refresh Package details for an SSISDB task.
We have an identical setup that works fine. Both are freshly installed machines where backuped up settings were imported.

We're running VisualCron 8.1.1 on Win2016 , the SSISB (SQL2016) resides on the same server. When we try to refresh the SSISDB Package details we get the following error message:


We've already tried the following:

* Uninstall VC 8.1.1, Install 8.1.1, import settings: --> Failed
* connect to the SSISDB on the working machine using VC on the failing machine: --> failed
* connect to the SSISDB on the failing machine using VC on the working machine: --> Worked

This leads us to believe the problem originates from VC on this particular machine.

Can you please help to resolve this problem? We are not able to schedule any new developments. 😞

Turn on Extended debugging in Server settings. Try to refresh. Check the log file log_serverDATE.txt for errors.

We also recommend that you upgrade to a later version for better debugging.

---

Henrik,

As it turns out Extended debugging was already activated.
The Error that occurs is the following:



I will talk to our admin to see about upgrading.

Hans

---

Looks like a classic dll hell problem you have there. The runtime is looking for a particular version of Microsoft.SqlServer.ConnectionInfo, but cannot find it. VisualCron has a version of this in it's installation folder, and this can create a conflict if you have a program looking for a different version. I've had to deal with this many times. One quick try is to add the version it is looking for (11.0.0.0) to the GAC, and see if it works. For more details you should run Fusion (Fuslogvw.exe) when the error occurs. It will give you the details of where it is looking for the assemblies. It's a complex topic as i looks in machine.config, app.config, the GAC and several other places.

Henrik,

As it turns out Extended debugging was already activated.
The Error that occurs is the following:

12/06/2017 15:04:24	Err	Select case ex: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.SqlServer.ConnectionInfo, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.IDKINILANOIIHIDOPEGABIFMCMDAGBLLPGEF.CCBBJKPIFFFOIAPHKLKFOOLACEICHAHDDIDM(MessageClass  , String  )
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.IDKINILANOIIHIDOPEGABIFMCMDAGBLLPGEF.NGDICPMEJLCANMBOGJNOFJFKFJILGPGFFCPB(MessageClass  , String  ) in C:\sourcefiles\code\VisualCronService\Jobs\TaskProcesses\Database\clsProcessTaskSSISDB.vb:line 79
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.FCAGFFJBIPDCJFIIPJFLJDAMAMIJDMPBDLCI.KAKDJOHMMLDIAKLOEANIFIKOMHPEMDFAJMBC(String  , MessageClass  , Byte[]  , Boolean  ) in C:\sourcefiles\code\VisualCronService\Connection\apiMessage.vb:line 507

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

I will talk to our admin to see about upgrading.

Hans

Thanks, I can confirm that same version referenced is in the folder of version 8.2.7.

---