I Cant Launch LoadRunner 11.5 - exception

I'm having a problem launching the trial version of LoadRunner 11.5. It says:
An unhandled exception has occurred in your application. If you click continue, the application will ignore this error and attempt to continue. If you click quit, the application will close immediately.
Retrieving the COM class factory component with CLSID
{CF405F74-4814-AD81-525877D8C9A0} Failed due to the following
error: 80040154 class not registered (Exception from HRESULT:
0x80040154(REGDB_E_CLASSNOTREG)).

Which component is failing? VUGEN? Controller? Analysis? Other?
Did this component ever work on this host? If not, then this is an installation or rights issue
Have you contacted vendor support? This assumes that you are under maintenance for your 11.5 version of LoadRunner.

Related

Windows Phone 8.1 throws a FileLoadException on startup

I'm currently building a Windows Phone 8.1 App (WinRT). I can build it in Debug Mode in Visual Studio 2013 without any problems. It is also runs in the emulator and on a real device. But when I build the app in Release mode it crashes instantly on both the emulator and the device.
In the Debug Output windows of Visual Studio I can see that a FileLoadException is thrown on startup. This means:
The exception that is thrown when a managed assembly is found but
cannot be loaded.
https://msdn.microsoft.com/de-de/library/system.io.fileloadexception%28v=vs.110%29.aspx
Unfortunately I can not see which assembly causes the problem! Is there any means to make the information visible?
A first chance exception of type 'System.IO.FileLoadException' occurred in MarketIQ.exe
A first chance exception of type 'System.IO.FileLoadException' occurred in mscorlib.ni.dll
'MarketIQ.exe' (CoreCLR: .): Loaded 'C:\windows\system32\en-US\mscorlib.debug.resources.dll'. Module was built without symbols.
A first chance exception of type 'System.ArgumentException' occurred in mscorlib.ni.dll
A first chance exception of type 'System.ArgumentException' occurred in mscorlib.ni.dll
'MarketIQ.exe' (CoreCLR: .): Loaded 'C:\Data\SharedData\PhoneTools\AppxLayouts\c53a5ef4-9f4f-4a1d-a5f4-2e73b5806daeVS.Release_AnyCPU.oprins\Log.Model.Client.DLL'. Cannot find or open the PDB file.
The program '[3020] MarketIQ.exe' has exited with code -1073741189 (0xc000027b).
The problem was device dependent. The app now runs smoothly after a factory reset.

Brokered Component not working when deploying to client

I created a test App with brokered copmonent and it runs smooth on my machine, but when moved it to a tablet and did all the required settings (regsvr32, icacls), it throws an exception. then I went and downloaded the Microsoft Northwind sample and it act the same. works fine on my machine but not on the other tablet. Am I missing any thing here? here is the exception, it's casting exception and Access denied exception:
Unable to cast COM object of type 'NorthwindRT.DAL.FileWatcher' to interface type 'NorthwindRT.DAL.IFileWatcherClass'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{23F40340-AEB1-5774-5705-64488C9BDD3A}' failed due to the following error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
but I did on the tablet the same things I did on the developing machine!
I moved the required files to the correct directory and enabled read/execute to all applications and I registered the proxy using regsvr32. Also the user can access the directory where the implementation dll is located so Access is denied exception is weird.
I did my research about brokered comp and I am doing exactly like the available documentations!
Any Ideas? Am I missing anything here? Is there extra settings I need to do? is my system missing any required dlls?
The App does not have access to msvcr120d.dll
add "ALL APPLICATION PACKAGES" to this dll and it will solve the issue.
I am also working on brokered component, so far I did had some success in development as well as deployment.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
You need to run icacls in the folder where you have the proxystub.dll and the winmd implementation.
icacls . /T /grant "ALL APPLICATION PACKAGES":RX
Now if you're deploying to a device that does not have a dev environment (i.e. Visual studio), you need to install Visual C++ Redistributable for Visual Studio 2015 (you can use whatever VS version you have, it just happend that i am using VS2015). You can download it here. And one more thing, since you don't have a development environment in the device, you would like to deploy Release assemblies not Debug so that the assemblies won't be referencing libraries or dll that is for debug (i.e. msvcr120.dll instead of msvcr120d.dll) because it won't be found in a clean device.
Lastly, I have a blog about brokered component. You might want to check it out.

Windows Phone 8 Application doesn't run if installed from Market

I have a strange problem. I have a windows phone 8 application, which is successfully installed on the phone under Visual Studio and works. If I deploy my xap using deployment tool it also works. It is successfully submitted on market. But when I download the app on the same phone from market it fails to run. It writes "load....." and that's all.
What may be reason of such behavior?
It is a Beta version? or a certified Version?
If it's just a beta version you can create a "logger" for catch all error when you quit your application in
App.xaml.cs::Application_UnhandledException
and in
App.xaml.cs::RootFrame_NavigationFailed
this is a sample:
private void Application_UnhandledException(object sender, ApplicationUnhandledExceptionEventArgs e)
{
// Call your logger class for catch the message exception before application was killed.
Logger.Debug(e.ExceptionObject.Message);
if (System.Diagnostics.Debugger.IsAttached)
{
// An unhandled exception has occurred; break into the debugger
System.Diagnostics.Debugger.Break();
}
}
You juste save the message, or/and the stackTrace and send you the error by mail.
Also, you can try publish your application on "hidden" on the store.
If the certification team can launch your application, and they're found no error, you can download it with your link. And try to install in your device.
Else, the team found an error, you received a documentation explain why your certification failed...
If it's an Certified Application, I've no Idea for this bug... :'( Maybe you call a invalid server when the application launch or a other error launch an exception?? But It's strange that work with VisualStudio and the .xap deployement...
If you find the solution of your problem, I'm interested :-)

Monodevelop 2.8.6 on windows

I hope someone can answer this as its driving me crazy. I have installed Monodevelop on windows XP. The version being 2.8.6.5. I set the default/active runtime as Microsoft .Net and set my projects to target .net 4.0 via project settings BUILD-->General->Target framework.
When I debug it from the application output window it loads XSP 2.0 and tries to the old .Net 2 DLL's ie from the .Net 2 GAC - C:\windows\assembly instead of the .Net 4 GAC.
when I debug setting Mono as the active runtime it works ok.
I get the error, which is understandable given the fact the build is targeting .Net 4 yet its looking at the wrong runtime:
Could not load file or assembly 'TestWeb' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
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.BadImageFormatException: Could not load file or assembly 'TestWeb' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
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.
Here is the output from the Output window:
Loaded Module 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll'
Started Thread 1872
Loaded Module 'C:\Program Files\MonoDevelop\bin\xsp2.exe'
Loaded Module 'C:\WINDOWS\assembly\GAC_MSIL\MonoDevelop.Xsp\2.8.0.0__0738eb9f132ed756\MonoDevelop.Xsp.dll'
Loaded Module 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll'
Loaded Module 'C:\WINDOWS\assembly\GAC_32\System.Web\2.0.0.0__b03f5f7f11d50a3a\System.Web.dll'
Loaded Module 'C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'
Loaded Module 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll'
many thanks
Simon.

Diagnosing CLR errors in Windows Event Viewer

We have an .NET desktop application that crashed in production. How do we diagnose the error? I'd like to know the type of exception that occurred, the error message, and the stack trace.
Because the exception wasn't handled by our code, we received the "This application has encountered a problem and needs to close" Windows message box. The only option was to close, there was no debug button.
This MSDN article suggested looking in the Windows Event registry. I checked there, and here's the information inside it:
Faulting application Initect.Server.UI.exe,
version 0.12.9084.90,
time stamp 0x49cac472,
faulting module KERNEL32.dll,
version 6.0.6001.18000,
time stamp 0x4791a81d,
exception code 0xe0434f4d,
fault offset 0x0002f35f,
process id 0x44c,
application start time 0x01c9ada7f320cab0
How can this information tell me the exception type, the stack trace, and the error message?
That information isn't enough to get you a stack trace, exception type, error message, etc.
You can configure Windows Error Reporting (which showed you the problem & needs to close UI) on Windows Server 2008 to always collect a dump file that you can then debug. This doesn't require you to install Visual Studio or any other debugger in your production environment.
http://blogs.technet.com/askperf/archive/2008/02/05/ws2008-windows-error-reporting.aspx shows the proper registry settings to do this.