Ask a Question

Test fails in TestExecute on VM

Kostja
Contributor

Test fails in TestExecute on VM

Hi everybody,

 

i wrote the a test just to verify the connection with the database:

 

var Cmd = ADO.CreateADOCommand();
  Cmd.ConnectionString = "Driver={Microsoft ODBC for Oracle};"
                        + "Server=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=199.199.199.199)(PORT=1523))(CONNECT_DATA=(SID=SID)));"
                        + "Uid=user;Pwd=password;"
  
  Cmd.CommandText = "SELECT * FROM table1 WHERE anr = 112640";

  Cmd.Execute();

 

Everything works fine on my computer (TestComplete and TestExecute), but when i execute the same test in TestExecute on the VM, the test fails with following description --> [Microsoft][ODBC driver for Oracle][Oracle]ORA-06413: Connection not open

 

I tried to modify the Firewall and start TestExecute with admin rights, but it didn't help. The needed Drivers are also installed (except for the Oracle in OraClient11g_home1)

 

Can anybody give me an advice what the causes TestExecute to fail on the VM?

 

The VM runs with Windows 8.1 Pro. My Computer runs with Windows 10 Pro.

2 REPLIES 2
Marsha_R
Community Hero

Sounds like the VM can't see the machine where the database lives.  Try it without TE, ping or some other connection make sure those two machines can communicate first.


Marsha_R
[Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame

The solution was to configure the Oracle driver properly and to set a System DSN variable.

 

 

cancel
Showing results for 
Search instead for 
Did you mean: