Post migration of VC++ project from VS2010 to VS2019 - application is throwing error while running

Question

Post migration of VC++ project from VS2010 to VS2019 - application is throwing error while running

Chandra Sekhar K 40

After migration a VC++ windows service from VS2010 to VS2019, when I try to run the application (Debug mode) I am getting error like

RuntimeError

Project has both libraries orasql9.lib and orasql12.lib. But, we will be using only orasql12.lib only. So, I have excluded orasql9.lib from build from file properties and included orasql12.lib for build.

Even I have tried to remove the ora 9 library but no luck. With the release mode, it is giving same error for orasql12dll.

My VDI is already having Oracle 12 client installed.

Please suggest if I am missing any component in my machine. I am from .net background and new to VC++.

Viorel 122.6K Reputation points

2023-03-24T10:46:02.47+00:00

The Project Properties dialog depends on configurations and platforms that can be selected from dropdown lists. Maybe you did not adjust all of configurations and platforms.
Chandra Sekhar K 40 Reputation points

2023-03-29T11:18:28.77+00:00

Thanks Viorel. I have made changes to project properties (linker>Input) and both Debug/Release mode are giving the same error related to orasql12.dll now.

I am trying to resolve that error. Orace 12 client is already installed in my machine (32 bit). I got to know from some other forum that orasql12.dll should be present under C:\windows\SysWOW64 folder.
Viorel 122.6K Reputation points

2023-03-29T11:57:26.5166667+00:00

I think that the DLL file can be also copied to the folder of your EXE.

Maybe the DLL depends on other libraries, which must be present too.

You can also check if a modified application works as a console or desktop program.
Chandra Sekhar K 40 Reputation points

2023-03-29T19:47:17.69+00:00

Thanks for your reply. DLL and libraries are present and the application is a windows service. I have added Oracle dll path to PATH environment variable as per RLWA32 suggestion and it cleared the error dialogue. I am able to debug and check now. Thanks for your help too.

Accepted answer

0 additional answers

Your answer

Viorel 122.6K Reputation points

2023-03-24T10:46:02.47+00:00

The Project Properties dialog depends on configurations and platforms that can be selected from dropdown lists. Maybe you did not adjust all of configurations and platforms.
Chandra Sekhar K 40 Reputation points

2023-03-29T11:18:28.77+00:00

Thanks Viorel. I have made changes to project properties (linker>Input) and both Debug/Release mode are giving the same error related to orasql12.dll now.

I am trying to resolve that error. Orace 12 client is already installed in my machine (32 bit). I got to know from some other forum that orasql12.dll should be present under C:\windows\SysWOW64 folder.
Viorel 122.6K Reputation points

2023-03-29T11:57:26.5166667+00:00

I think that the DLL file can be also copied to the folder of your EXE.

Maybe the DLL depends on other libraries, which must be present too.

You can also check if a modified application works as a console or desktop program.
Chandra Sekhar K 40 Reputation points

2023-03-29T19:47:17.69+00:00

Thanks for your reply. DLL and libraries are present and the application is a windows service. I have added Oracle dll path to PATH environment variable as per RLWA32 suggestion and it cleared the error dialogue. I am able to debug and check now. Thanks for your help too.

Answer 1

RLWA32 49,636

Since your question relates to third party software (Oracle) I cannot say whether your code should be using both Oracle 9 and Oracle 12 or only binaries from one version.

The System Error message indicates that your code is using load-time linking for the Oracle dlls. From what has been said it seems that the Debug configuration is using Oracle 9 and the Release configuration is using Oracle 12. This apparently contradicts the statement "But, we will be using only orasql12.lib only." So you need to resolve this inconsistency for your Oracle usage and configure your project properties accordingly. As @Viorel has pointed out VS maintains separate project property settings for the various combinations of Platform/Configuration so make sure that you are adjusting the properties for the correct combinations. Sometimes its easier to adjust properties for All Platforms and All Configurations.

As far as the run-time System Error is concerned, this indicates that the dlls in the error messages could not be located by the system when the .exe is loaded. You need to verify the file system location of the indicated Oracle dlls and ensure that location is one that will be searched by the system when loading dlls at run-time. The system search order is documented at Dynamic-link library search order.

Chandra Sekhar K 40 Reputation points

2023-03-29T11:27:42.86+00:00
Thanks for your reply @RLWA32 . As per Viorel suggestion, I have made some changes to project properties related Linker and both modes (Debug and Release) shows the same error.

As per the code, it is indicating linker to user orasql12 lib (orasql12.lib) as I have already defined ORACLE_12 in properties.

#ifdef ORACLE_12// use Oracle 12 client library #pragma comment(lib, "oraSQL12") #else #pragma comment(lib, "oraSQL9") #endif

In one of the forums, someone has mentioned that orasql12.dll should be placed under C:\Windows\SysWOW64 folder in order to be used in project etc. I am trying it out. Due to admin privileges in VDI, I am working with VDI team on the same.

Any thoughts on this if this understanding is correct or not?
RLWA32 49,636 Reputation points

2023-03-29T11:47:42.2133333+00:00

Well, if the Oracle binaries are 32-bit dlls then C:\Windows\SysWOW64 makes sense. In this case you need to build 32-bit applications. Otherwise, if they are 64-bit dlls then C:\Windows\System32 seems appropriate and 64-bit applications should be created.

You can independently verify the bitness of the Oracle dlls using tools like DUMPBIN or Sigcheck from Sysinternals.

Another option is to include the path to the Oracle dlls in the PATH environment variable.
Chandra Sekhar K 40 Reputation points

2023-03-29T19:43:08.25+00:00

Thanks for your suggestion. 32-bit Oracle binary is available in my machine. As per your suggestion, I have included the Oracle dll path in "PATH" environment variable and able to debug without error debug.
Chandra Sekhar K 40 Reputation points

2023-04-12T17:27:44.0566667+00:00

Hi @RLWA32 , I have posted another question related to another vc++ service migration as the current problem is solved and I have accepted answer too. Please assist or provide your suggestions. Thanks in advance and sorry for the trouble. "https://learn.microsoft.com/en-us/answers/questions/1226256/vc-project-migration-build-error-from-vs2010-to-vs".

Share via

Post migration of VC++ project from VS2010 to VS2019 - application is throwing error while running

0 additional answers

Your answer