I'm trying to create a .NET 3.5 Console Application that uses the Business Objects XI3.1 .NET SDK. I've pulled in all libraries needed to compile the application.
I'm compiling in Visual Studio 2012, on Windows 2008 64-bit.
When I call into get a new 'SessionMgr' an error occurs.
Try
sm = New SessionMgr
Catch ex As Exception
'Error Shown below
End Try
Error:
Retrieving the COM class factory for component with {CLSD 3EBB7859-E4E3-4D77-B673-C6E5AD529CC1} failed due to the following error:80040154
The BusinessObjects SDK code is compiled against x86, and if you try to run this code on an 64-bit machine, there will be an error unless you compile the program only to run in x86 mode.
To compile in x86, you need to go into your project settings, and change the Target CPU to be x86.
Related
A C++ app crashes (only on our develop pc's where we have also VisualStudio, in all others works fine) after few second from startup. If we run it on debug we an Kernelbase.dll Module not found exception, last call at MSO.DLL!__delayLoadHelper2(). At the moment of the crash the app already loaded all the databases it use.
Tried to update all: windows, Microsoft365, visual studio etc.
Change Provider from 12.0 to 16.0
Installed Microsoft 365 Access Runtime and Microsoft Access 2013 Runtime (with these is also impossible to use Access app)
First, I'm new with programming.
I have already builded a successful solution in my own computer with Visual Studio 2013 with Armadillo and LAPACK/BLAS. I'm able to run both Console Application (.exe) and (.dll) in my system (Windows 7).
The problem arrived when I needed to run those application in a different computer with Windows 7. First, every application that i build was throwing the error "MSVCP120D.dll is missing in your computer". I was able to fix this changing "Runtime Library" in VS from MDd(MD) to MTd(MT). With this method I could run a console application with Armadillo, but without the use of LAPACK/BLAS (uncommenting the respective line in config.hpp)
When I enable the use of LAPACK/BLAS with the MTd(MT) Runtime configuration in VS2013, the application no longer run in this different computer.
So, what I'm doing wrong and what to do in this case?
Thanks!
I have a vs 2008 c++x32 build and when I tried to run it on a fresh windows 7 vm install, I get the following error:
"WINDOWS 7 error The application has failed to start because the side
by side configuration is incorrect please see the application event
log or use the command line sxstrace.exe tool for more detail."
I have found the following resolution:
The machine is missing the correct C++ runtime components for your
type of system. (x86 or x64). Installing the following update resolves
the issue. Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
As details about the vs 2008 solutions: i use unicode, I don't use ATL or MFC just Standard Windows Libraries.
My question is: am I doing something wrong? is this normal or there is a way of overcoming this problem from the development phase. What must I do so that my program would run the first time.
All programs compiled from Visual Studio needs a runtime library (the library that actually contains the functions used by new, delete and other runtime support functions). This runtime library needs to be there when you run your program. Either by you installing the shared libraries, or by you making your project a statically linked project so the runtime is linked to your program.
So I have this small application of mine I'm trying to deploy using visual studio. I have Intel parallel studio 2011 added to visual studio, and I'm compiling this program using Intel within VS because I'm using OpenMP task construct which is not supported in VS2010. I added a deployment project to my solution and built a setup. Dependencies are detected as follows:
glu32.dll opengl32.dll and libiomp5md.dll
Now I'm trying to test this setup file to see if it works. I have Windows XP Mode installed and I access the setup file, I setup my application, decencies are copied just fine but:
When I try to run the application first time I got an error saying:
The entry point _ftol2 could not be loacted in the dynamic link library msvcrt.dll
I found solution to this problem by removing glu32.dll and opengl32.dll and adding glut32.dll to my windows/system folder.
But then it comes up with this second error saying:
The application or dll ".....\libiomp5md.dll" is not a valid windows image. please check this against your installation diskette
again I googled and I got this and it didn't work.
Reminder: I'm using Win7 x64 and Visual Studio 2010 with Intel Parallel Studio 2011.
I guess you need to install the redistributable libraries on the target machine.
I have a Win32 C++ Application using a handful of third-Party DLLs that is installed at some hundred costumer machines. I recently tested the x86 Version of the installation successfully on Windows XP, Windows Vista x64, Windows 7 x86 as well as Windows Server 2008 x86. No Problems. The Installer (nullsoft) installs the redistributable files for VC 2005 and VC 2008 as both are required by different DLLs we use.
But with Windows Server 2008 x64 both, the x86 and the x64 Versions refuse to start.
When i start the x86 Version of the program a Dialog appears:
<myApp> has stopped Working.
The EventLog contains a message:
Faulting application myapp.exe, version 1.0.0.0, time stamp 0x4bcb37ca,
faulting module MSVCR80.dll, version 8.0.50727.4053, time stamp 0x4a594c79,
exception code 0xc000000d, fault offset 0x0001ce0b, process id 0x29c,
application start time 0x01cb0329976cfc68.
\Windows\winsxs contains a directory
x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d
Using sxstrace (first trace, then parse) a log file of 3 Bytes length is created containing non readable characters. Behavior of the x64 Version is similar. Also all demo programms from the 3rd Party Dlls are working properly. Any hint ?
It doesn't look like a side-by-side error. The exception code is STATUS_INVALID_PARAMETER, "An invalid parameter was passed to a service or function." That doesn't help. You'll need a debugger, probably with the Windows debugging symbols. Make it stop on the first-chance exception.