User Guide & Application Administration Guide
Collecting Browser Performance Information
"HTTP 405 - HTTP verb used to access this page is not allowed", Resolution
PostInstall Tasks - Common Logging Issue
Troubleshooting Integration Issues - Using Fiddler
Troubleshooting Requirement Synchronization
Troubleshooting Common Installation Issues
Troubleshooting 64-Bit Installations
Updates required after changing the JIRA Server URL
- Collecting Browser Performance Information
Earlier Versions of this Documentation
Support & Bug Fixes
When upgrading or installing ET, some files may need elevated permissions. When these permissions are not available some files may not be installed correctly. One example is the PostInstallTasks.exe. Here are the steps to resolving this this issue. The new upgrade installation files in V4.6 address this issue but, it may still occur when running the .msi installation file only.
The assembly 'Common.Logging, Version=126.96.36.199, Culture=neutral, PublicKeyToken=af08829b84f0328e' could not be loaded.
Steps to Resolve
1. Backup the web.config file.
2. Start a command prompt (run as administrator), then change to the root directory of ET install using this command:
cd "c:\Program Files (x86)\Catch Limited\Enterprise Tester"
3. Run the following command:
You should see this message, confirming you are in the correct directory:
c:\Program Files (x86)\Catch Limited\Enterprise Tester>PostInstallTasks.exe Expected a single argument of either 'installation' or 'ziprelease'
4. Run the following command:
This should run (silently) and will patch the web.config file with the necessary changes to the web.config file.
Now try to access ET in your web browser it should start up correctly.
If you still have problems with starting up, email your web.config file through to Catch Support for review. The PostInstallTasks should add a section to the bottom of the web.config that looks like this:
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Common.Logging" publicKeyToken="AF08829B84F0328E" culture="neutral"/> <bindingRedirect oldVersion="0.0.0.0-188.8.131.52" newVersion="184.108.40.206"/> </dependentAssembly> </assemblyBinding> </runtime> </configuration>
This is what removes the error related to the common logging version mismatch.