I don't know how I do it, but I think I can find the strangest bugs and always at the last minute.



I had everything built and had completed my QA testing. Everything functioned great, the BrokenRule issue was resolved. So, I moved all my files into the staging area. It's just a different directory on the same server, same hard drive. I set up a second QC/staging Web site and started clicking through to make sure permissions were all set up and working the way they did on the development site and I had some more issues.



As I said, this is on the same server and the same hard drive, just a different file path. I made sure all my config values were updated to use the new path for logging and database login information (still connects to the same database, but accesses a file in a different path location). It logs in, gets me data and works fine. When I try to save something, for example, modified application permissions for a role, it blows up.



I finally tracked it down to it claiming the transaction key didn't exist. I double checked and it starts the transaction. I added some code to conditionally use the transaction if it exists. So I check the Transactions collection for the key and if it exists, I tell the business object to save using the transaction. If it doesn't, I have it save without a transaction. It detects that there is a transaction and then throws an exception that the key does not exist. Here's the stack trace:







And here's the Exception and Inner Exception that get thrown:







I'm thoroughly confused about this one since it all works fine and lets me save in the development area, but not in the QC area. They reference the same Strataframe assemblies and the same IBM.Data.DB2 assembly. It was just a straight copy of the files from one directory (D:\Dev\Application\) to another (D:\QC\Application).



Any ideas what could be causing this?



Thanks!