Unable to Install Client Side QC 10.0 - hp-quality-center

Unable to Install Quality Center Client Side on the client's machine.
Operating System: Windows Vista
IE Version:9
We tried all the basic trouble shooting steps like deleting TD_80 folder from %temp% and performing a fresh installation.
Deleting Mercury Intercative folder from
C:\program files\common files
Running the internet explorer as Administrator.
None of the above solved the problem
we are recieving the below error message:::::
HP Quality Center: Unrecoverable Error Occured.
Reason: Could not load file or assembly 'interop.OTAClient, Version=10.0.02469,Culture=neutral, PublicKeyToken=792843134cf0407a' or Contact your site administrator.
Details::::
System.IO.FileNotFoundException: Could not load file or assembly 'interop.OTAClient, Version=10.0.0.2469, Culture=neutral, PublicKeyToken=792843134cf0407a' or one of its dependencies. The system cannot find the file specified.
File name: 'interop.OTAClient, Version=10.0.0.2469, Culture=neutral, PublicKeyToken=792843134cf0407a'
at Mercury.TD.Client.Ota.Core.Application.SSPREnabled(String serverUrl)
at Mercury.TD.Client.UI.Core.Services.ConnectionManagementService.Initialize()
at Mercury.TD.Client.UI.Core.Services.BaseService.Initialize(IServiceManager serviceManager)
at Mercury.TD.Client.UI.Core.ServiceFactory1.CreateService()
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.b__0()
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.CreateService(ServiceConstructorDelegate1 serviceConstructor, T& service)
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.GetServiceEx(ServiceConstructorDelegate1 serviceConstructor)
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.GetService()
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.GetBaseService()
at Mercury.TD.Client.UI.Core.ServiceManager.DoPublish[T](IServiceFactory1 factory, Boolean activate)
at Mercury.TD.Client.UI.Core.ServiceManager.PublishAndActivate[T,C]()
at Mercury.TD.Client.UI.Core.ApplicationServicesPlugin.PublishServices(IServiceManager serviceManager)
at Mercury.TD.Client.UI.Core.Services.ApplicationService.InitializePlugins()
at Mercury.TD.Client.UI.Core.Services.ApplicationService.Start(Application application)
at Mercury.TD.Client.UI.Core.Application.Start()
at Mercury.TD.Client.UI.Core.Application.Initialize(String url, String configFilePath, IDictionary2 properties)
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].

Use the Quality Center Explorer Add-In rather than the one tied to the browser:
ALM Explorer 11
QCExplorer 10
QCExplorer 9
QC Forums

Related

BizTalk Health Monitor

I'm trying to run the "Analyze Now" on BHM50.exe (BizTalk Health Monitor) on BizTalk 2016.
I opened as Administrator, and I should have all the necessary privileges.
We have two BizTalk servers in a group, with SQL on a different machine.
It gives this error.
Launching "D:\Program Files (x86)\BizTalkHealthMonitor\BHMCOLLECT.EXE"
-PROFILE:C:\PROGRA~3\MICROS~1\BIZTAL~2\MBVSET~1.XML
Unhandled Exception: System.IO.FileLoadException: Could not load file
or assembly 'MYHC, Version=11.0.0.0, Culture=neutral,
PublicKeyToken=fa6906311f4bb5cd' or one of its dependencies. The
located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040) at
MyHealthCheck.Class1.Init(String[] args)
There were no matches at all on Google for this error.
Sample screen shot:
It's complaining about MyHC - does it need to be put in the GAC?
Here it is in the same directory where I installed the utility.
You have this error when one of the BHM components is not "compatible" with the others. This issue can occur during a partial self-update of BHM.
When you update BHM using its self-update features, be sure that all the components proposed in the update were well downloaded; if only a part of them is downloaded in the BHM folder, you will have this kind of error at the BHM startup or collect start.
If you redownload and reinstall BHM, you should not meet this error but you will have to self-update BHM to have its latest components downloaded (queries/rules repository, collect engine, MMC snapin, etc...)
JP (BHM Dev team)
Try to update to the latest version. There is an option for that RC/BHM Update

Visual Studio 2010 compile error

I am getting the following error when I compile the release of my web application. The project ran fine previously on another machine the hard drive went out on. So I am thinking there is a problem with the configuration. I did some research and it made note of a Web Deploy issue but I am unable to verify what version was in use on the past machine.
Here is the error:
The "IsCleanMSDeployPackageNeeded" task failed unexpectedly.
System.InvalidCastException:
[A]Microsoft.Web.Deployment.DeploymentProviderOptions cannot be cast
to [B]Microsoft.Web.Deployment.DeploymentProviderOptions. Type A
originates from 'Microsoft.Web.Deployment, Version=9.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context
'Default' at location
'C:\Windows\assembly\GAC_MSIL\Microsoft.Web.Deployment\9.0.0.0__31bf3856ad364e35\Microsoft.Web.Deployment.dll'.
Type B originates from 'Microsoft.Web.Deployment, Version=7.1.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context
'Default' at location
'C:\Windows\assembly\GAC_MSIL\Microsoft.Web.Deployment\7.1.0.0__31bf3856ad364e35\Microsoft.Web.Deployment.dll'.
at Microsoft.Web.Deployment.ArchiveElementHelper.get_ProviderContext()
at
Microsoft.Web.Deployment.ZipPackageProvider.d__0.MoveNext()
at
Microsoft.Web.Deployment.DeploymentObject.d__9.MoveNext()
at
Microsoft.Web.Deployment.DeploymentObject.d__0.MoveNext()
at
Microsoft.Web.Publishing.Tasks.IsCleanMSDeployPackageNeeded.CheckMSDeployDumpContainIisSetting(DeploymentObject
deploymentObject, String& iisMSDeployProviderName) at
Microsoft.Web.Publishing.Tasks.IsCleanMSDeployPackageNeeded.Execute()
at
Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at
Microsoft.Build.BackEnd.TaskBuilder.d__20.MoveNext() 0 0 PKL_QMW
Apparently this can happen if you install the Web Deployment package without the UI Components.
Try going into add remove programs and doing a Change install on 'Microsoft Web Deploy' and ensure that the UI components are selected to install.

When I deploy my web project on IIS, I get the following error

When i deploy my web project after publishing, on IIS. it gives me the following error.
Server Error in '/' Application.
Could not load file or assembly 'System.Web' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'System.Web' or one of its dependencies. The system cannot find the file specified.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web' could not be loaded.
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].
Try the following (If using 64 bit IIS - replace framework by framework 64):-
Run command prompt as admin.
2a. If using version 3.5 Type
cd c:\windows\microsoft.net\framework\v2.0.50727
and press enter.
2b. If using version 4.0 or 4.5 type
cd c:\windows\microsoft.net\framework\v4.0.30319
and press enter.
3. Type
aspnet_regiis -i
and press enter.

Remote execution of Coded UI Tests on a Windows XP VM

I have a Coded UI + SpecFlow test project (.NET Framework 4).
I want to perform remote test execution, so I configured a Visual Test Agent - Controller environment setup. My local machine is the Controller and there is a virtual machine which is the agent. The AUT will run on a Windows Embedded System with Windows XP SP3. The AUT is a WPF application.
VM properties:
Windows XP SP 3
Microsoft Test Agent 2012 is installed on the VM (Agents for Visual Studio 2012 Update 3)
The agent-controller communication is established successfully (Agent - Online, OK; Controller - Running, OK; TestSettings.testsettings - Configured, OK). The test execution is performed using mstest.
The following error is displayed when I execute the tests:
Test Name: CodedUITestMethod1
Test FullName: Remote.Test.CodedUITest1.CodedUITestMethod1
Test Source: c:\Users\user\Documents\Visual Studio 2012\Projects\Remote.Test\Remote.Test\CodedUITest1.cs : line 27
Test Outcome: Failed
Test Duration: 0:00:01.7131241
Result Message: Error calling Initialization method for test class Remote.Test.CodedUITest1: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.TestTools.UITest.Extension.CrossBrowser, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
Result StackTrace:
--- End of inner exception stack trace ---
at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
at System.Reflection.Assembly.LoadFile(String path)
at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestExtensionPackageManager.LoadAssembly(String assemblyFile)
By definition Coded UI does not support Windows XP.
Is there a workaround for the upper mentioned issue? Any suggestions?
Thank you,
Isolation of Microsoft.VisualStudio.TestTools.UITest.Extension.CrossBrowser.dll from c:\Program Files\Common Files\microsoft shared\VSTT\11.0\UITestExtensionPackages\ solved the problem. Action was performed on the remote VM.
The tests are up and running.

HttpHandlers x64 problem

I developed a .Net 3.5 x64 web application that includes a custom HttpHandler in the config:
<add path="*.class1" verb="GET" type="ClassLibrary1.Class1Handler"/>
This works when the platform target for ClassLibrary1 is set at x86.
However, when I set this to x64 I get the following error when I run web application starts (it compiles just fine):
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'ClassLibrary1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Does this mean that a HttpHandler can be compiled at x86 only?
That doesn't make much sense to me.
Does anyone have an idea of what could be going on?
Edit 1:
The ClassLibrary1 project is just an empty class library project with a single HttpHandler added (which is also empty).
Edit 2:
I am also getting these warning messages when compiling, I am pretty sure they have something to do with this problem:
Assembly generation -- Referenced assembly 'mscorlib.dll' targets a different processor HttpTest
Edit 3:
I manually edited the project file to force references to the x64 assemblies, like this:
<Reference Include="$(Windir)\Microsoft.NET\Framework64\v2.0.50727\System.dll"/>
This does supress the above warning message, but the problem isn't resolved.
Thanks!
You probably compiled your assembly ClassLibrary1 with the attribute x86. Try to compile it with AnyCPU tag.
One of your dependent assemblies is compiled with the flag set to x86 rather than AnyCPU or x64
See this page for how to use the coreflags.exe to query the assebly in question

Resources