Funky system.stackoverflow error when deploying

[jfrost10]

Hey guys,

ok, check it out:

we're trying to move our app to the production server. Here are my steps:
1. change the connection string in the dll
2. rebuild the dll
3. delete the reference to the dll in my app
4. re-reference the dll (so the new build takes effect)
5. rebuild the app
6. project>copy>copy only files necesarry to run, and dump
them into another folder (within IIS)

Now here's the problem:
If I try this, but leave the development dataabse connection string in, it works no problem from its copied virtual folder. If I put the production connection string in though, it craps out the first time I try and open a connection, and gives me this:

Unhandled exception of type 'System.StackOverflowException' occurred in system.data.dll

And if I continue running hte app, I get an "Server Application Not Available"

Any thoughts on why just changing a connection string would bunk up this badly?! I was expecting just an error saying that the database couldn't be found, but not this!

Just as an aside, if we do put this code up to the production server, it still does the same thing (and thats with the correct database being accessed)

HELP!

D'Arcy

 

[jfrost10]

All good.

It was my own code, had an infinite loop created.

sheesh.

D

 

[Zarcom]

gotta love them hey. That'l do donkey, that'l do
Mark
If you are unsure of forum etiquette check here faq796-2540

 

[jfrost10]

Bah! It was a nasty one too:

we have a custom exception class to log any sql exceptions and present meaningful messages to the users. When a sql exception is caught, it first checks the database to see if the exception number has already been recorded.

Well, if you put a bad connection string, a sql exception fires, then the exception class tries to check the database using THE SAME BAD CONNECTION STRING, which causes another error which creates an exception object which tries to check teh database using THE SAME BAD CONNECTION STRING, which...you get the picture


D