ERROR:
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].
After hours of frustration trying to determine why this suddenly stopped working out of the blue we had been running version 1.1 of the
websitepanel about a year with no problems.
Since either Connector/Net 6.4.3 or Connector/Net 6.3.7 produced the same results I found an
old article on the web and decided to try
Connector/Net 6.2.5. Well it did resolve that problem which I thought yeah I got it. Before assuming all was well I decided to try to install an application from the gallery but now it was failing.
Note:
After doing more testing we discovered that the old version 6.2.5 would correct the issue. However the first time a client would use WPI to install an application say WordPress for example. The system would automatically upgrade the connector back to 6.3.7. We have found
another article to use version 6.3.4 which is no longer available at from MySQL downloads. You can of course download it from the article above or we have also made it available
download here.
Solution:
Since reverting back to an earlier version is only a short term fix we found that this is the true long term fix to the problem. Go to this default path C:\WebsitePanel\Server open the web.config and add this in pink to the bottom and save the edited web.config you may wish to keep a backed up copy.
</system.serviceModel>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name ="MySql.Data" publicKeyToken="c5687fc88969c44d"/>
<bindingRedirect oldVersion="0.0.0.0-6.3.4.0" newVersion="6.3.7.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
ERROR:
Web Application Gallery module is unavailable:
So the frustration continues with a new twist. I decide that since websitepanel offered a new version 1.2.0. I did not have allot of hope for this since many people stated this did not happen to their server until they upgraded from 1.1.0 to 1.2.0.
After installing the new version of Websitepanel and uninstalling and reinstalling web deploy version 1.1 and version 2.0 Still the same error MsDeployIsNotInstalled. After doing more digging I found
this article which was the fix while nothing explains why this worked before and suddenly stopped. Changing the pools to 64 bit resolved the issue for both now which is about as odd as it gets.
I will say the one thing that has changed was MS patching 4 ASP.NET v4.0 and 1 ASP.NET v2.0 which I am sure they would say this could have no affect.