CVI Run Time Engine 6.0 Errors

[JAL]

I have a computer running Windows 2003 server.   I am unable to get the CVI runtime engine to work.   I tried a dist kit install and install the full development system on the PC.   Neither one worked.   With the distribution kit,   I got the following error:

Application failed to initialize properly   -- 0XC0000005.

I've had this same application in the same environment work fine.  This is a duplication of an existing test fixture.

Please give me any help you can

Thanks

Jonathan L

[JonathanN]

Hi Jonathan,

I first wanted to mention that Windows 2003 Server is not a supported OS for CVI.

However, with that said, typically when you see the "Application failed to initialize...." Windows message, this usually indicates your target machine is missing certain necessary components such as DLLs.  It makes sense it worked on your dev machine since you probably have those DLLs.  You see, when you launch your application, any statically linked component will also try to load as well (i.e. if you are linking against some DLL via an import library, that DLL will try to load when you app loads).  Therefore you need to make sure that you have that DLL on your target system.

You can use a free tool called Dependency Walker to determine what static dependencies your application has. 

Hope this helps!

Best Regards,

[Anonymous]

I had the same problem.
The problem is related to the CPU, not exactely the OS.
Is due to the new mechanism called *Data Execution Prevention *(check
this onyour PC ,SystemProperties--> AdvancedSystemproperties->Perfomance
options> Data Execution Prevention)
If you CPU support it, the CVI6 DLLs hangs.
I solved the problem simply downloading and installing CVIRTE8.5 that
is fully (!!) backward compatible.
Hope this helps
Raf


Jonathan N ha scritto:
> Hi Jonathan,
>
> I first wanted to mention that Windows 2003 Server is not a supported OS for
> CVI.
>
> However, with that said, typically when you see the "Application failed
> to initialize...." Windows message, this usually indicates your target
> machine is missing certain necessary components such as DLLs.  It makes
> sense it worked on your dev machine since you probably have those DLLs. 
> You see, when you launch your application, any statically linked component will
> also try to load as well (i.e. if you are linking against some DLL via an
> import library, that DLL will try to load when you app loads).  Therefore
> you need to make sure that you have that DLL on your target system.
>
> You can use a free tool called <a href="http://www.dependencywalker.com/" target="_blank">Dependency
> Walker</a> to determine what static dependencies your application has.&nbsp;
>
> Hope this helps!
>
> Best Regards,
>