Database Server Error
Error Message:
The description for Event ID ( 0 ) in Source ( WITS ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error:
Error#: -2147220501
Error Text:Unable to tie the query to the ADO connection.
Source: DB_Lib.SelectQuery
Receiving this error when executing any query.
Any ideas?
Thank you,
Wendee
The description for Event ID ( 0 ) in Source ( WITS ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error:
Error#: -2147220501
Error Text:Unable to tie the query to the ADO connection.
Source: DB_Lib.SelectQuery
Receiving this error when executing any query.
Any ideas?
Thank you,
Wendee
ASKER
Hmmm... My teammate said it is an Oracle error. Please let me reconfirm with him.
OH, that is a Windows event error.
Oracle error messages have a product designator followed by the error number.
For example: ORA-00942
>>ADO connection
This tells me it is some app like .Net trying to connect to a database. I assume in this case Oracle.
>>DB_Lib.SelectQuery
I have no idea what DB_Lib is and who makes it.
Oracle error messages have a product designator followed by the error number.
For example: ORA-00942
>>ADO connection
This tells me it is some app like .Net trying to connect to a database. I assume in this case Oracle.
>>DB_Lib.SelectQuery
I have no idea what DB_Lib is and who makes it.
ASKER
Oracle 11, he says.
>>Oracle 11, he says.
Did you not read my last post?
When I Googled "may be able to use the /AUXSOURCE=" it shows that is a Windows event type message.
Nothing posted points to Oracle as the source of the message.
Did you not read my last post?
When I Googled "may be able to use the /AUXSOURCE=" it shows that is a Windows event type message.
Nothing posted points to Oracle as the source of the message.
ASKER
Digging a little deeper:
The program was developed in VB 6.0 and is using an ODBC connection to Oracle 11.
The program was developed in VB 6.0 and is using an ODBC connection to Oracle 11.
ASKER
Sorry, the emails are not coming in from EE and I didn't refresh before updating. Please accept my apologies!
>>Please accept my apologies!
Accepted and apology wasn't necessary.
>>The program was developed in VB 6.0 and is using an ODBC connection
That would explain why there really isn't an Oracle error message.
I'll see what other zones might help.
Accepted and apology wasn't necessary.
>>The program was developed in VB 6.0 and is using an ODBC connection
That would explain why there really isn't an Oracle error message.
I'll see what other zones might help.
ASKER
Thank you slightwv!
ASKER
We don't need to close this out, right?
OK, back to the question:
Has this app ever worked?
If so, what changed?
If not, it might be a version issue of some type. I assume it had to run on a test server or at least the development server?
Has this app ever worked?
If so, what changed?
If not, it might be a version issue of some type. I assume it had to run on a test server or at least the development server?
>>We don't need to close this out, right?
Correct.
I just added more Zones to allow other Experts in those fields to help.
Correct.
I just added more Zones to allow other Experts in those fields to help.
ASKER
The app is working on the original server. There is a new server that this app is integrating to.
So, it has worked on one server, but not the new server.
Now that Oracle is ruled out, I am checking to see if it is a reference library issue, like I experience frequently in Microsoft Access VBA.
So, it has worked on one server, but not the new server.
Now that Oracle is ruled out, I am checking to see if it is a reference library issue, like I experience frequently in Microsoft Access VBA.
I've not ruled out Oracle. Only saying that Oracle isn't the one generating the error and if it is, the application isn't passing the Oracle information along.
It still might be an Oracle issue under the sheets.
>>but not the new server.
check bit versions, product versions, etc... between the old server and the new one.
Make sure what used to be 32Bit is still 32Bit and you aren't trying to mix and match 32 and 64.
Verify what products changed versions. ODBC requires an Oracle client install. Did the versions change?
Can you find out if DB_Lib is a 3rd party product? Maybe it isn't compatible with something new.
It still might be an Oracle issue under the sheets.
>>but not the new server.
check bit versions, product versions, etc... between the old server and the new one.
Make sure what used to be 32Bit is still 32Bit and you aren't trying to mix and match 32 and 64.
Verify what products changed versions. ODBC requires an Oracle client install. Did the versions change?
Can you find out if DB_Lib is a 3rd party product? Maybe it isn't compatible with something new.
ASKER
All servers are virtual on the same box. Would that rule out the bit conflict? 32 vs 64.
DB_Lib.DLL is a 3rd party product developed by someone here at our company. The source is unknown.
DB_Lib.DLL is a 3rd party product developed by someone here at our company. The source is unknown.
>> Would that rule out the bit conflict? 32 vs 64
No. Each VM has it's own OS. These can be anything.
No. Each VM has it's own OS. These can be anything.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We increased the MTS (TIME OUT) setting this morning from 15 minutes to 30 minutes. Now the queries are running and the connections are establishing. So it is working.
But we don't know why...
But we don't know why...
What product/language/??? is generating this error and I can see about finding additional zones for you.