System.InvalidOperationException: OracleConnection

Posts   
 
    
scottg
User
Posts: 12
Joined: 07-Dec-2006
# Posted on: 12-Dec-2006 00:41:18   

Can someone give me a quick read on this error? I have a working 2.0 application that just started giving me this exception error. I'm thinking it's a web server configuration problem, maybe something is wrong with the Oracle.net drivers?

System.InvalidOperationException: OracleConnection.ConnectionString is invalid at Oracle.DataAccess.Client.OracleConnection.Open() at..................

Sorry for not including my complete environment. I can if necessary, but I just thought this would be such an obvious problem to the right person that it might not be necessary!

Thanks in advance.

bclubb
User
Posts: 934
Joined: 12-Feb-2004
# Posted on: 12-Dec-2006 02:45:27   

I'm not the right guy simple_smile , but it may be helpful to get an example of the connection string. If you want you can email it to support at llblgen dot com or make a post in the helpdesk section with it.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39927
Joined: 17-Aug-2003
# Posted on: 12-Dec-2006 10:12:52   

Indeed, I think the connection string contents is essential here to spot the error. As you said the app worked but now doesn't, what has been changed to the connection string? If you want, post the connection string with the userid/password and servername CHARACTERS masked with 'a' like: User id=aaaaa;password=aaaaaa.

Frans Bouma | Lead developer LLBLGen Pro
scottg
User
Posts: 12
Joined: 07-Dec-2006
# Posted on: 12-Dec-2006 16:52:34   

Data Source=zzzzzz;user id=xxxxx;password=yyyyy

I believe the problem is with our Intranet web farm. One of the servers must not be configured correctly and some users are starting to hit the "bad" web server for some reason. There are two servers and they have some kind of fail-over or load balance config. I'm trying to get a conversation with the server guys going today to find out the setup and figure out a way to test each server. Will let you know what turns up, but it sure sounds like one of the servers is to blame. (PS: we keep our connection strings on the server in the registry and call that registry value from our apps)

Thanks

scottg
User
Posts: 12
Joined: 07-Dec-2006
# Posted on: 12-Dec-2006 17:41:00   

Yup, that was it. The secondary web server (the fail-over server) was getting "hit" sometimes when the primary was too busy, and it didn't have the connection string settings in place!

I hate it when that happens! simple_smile

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39927
Joined: 17-Aug-2003
# Posted on: 12-Dec-2006 19:06:00   

glad it's solved! simple_smile

Frans Bouma | Lead developer LLBLGen Pro