Click here to Skip to main content
15,885,757 members
Please Sign up or sign in to vote.
2.00/5 (1 vote)
I am total confused about this one.

I have an application that is running fine on a duplicate machine. The debug version runs fine on the troubled machine. The release version crashes during loading.

I can rename the release folder "debug" and the application runs fine.

This is an application running SQL R2 and various third party drivers.

Windows simply comes up with application failed and collecting data. Windows logs don't offer much assistance. I originally thought the problem was with reporting services but that has led nowhere.

Any ideas? I'll hunt down the details if anyone has any general suggestions.

Thanks,
Posted

1 solution

If it works when you rename the folder to 'Debug' is there any chance you have a hard coded path in there somewhere?
 
Share this answer
 
Comments
TenRC 21-Mar-11 22:47pm    
Henry, Thanks for your feedback.

That was my first thought. I do have a couple of SQL connection strings hard coded to another drive but I have search the solution and found no references to "debug" in the code. The kicker here is the same application is running on a duplicate system with no problem. I copied the solution and project directory from the original machine and placed it into the same location on the problem machine. The only thing different between machines is the pc name and I do not see any reference to pc names in any of the files.

HERE IS A LITTLE BACKGROUND ON THE APPLICATION:
Originally, the code ran fine for three or four weeks until I had a SQL failure due to compatibility issues between SQL Server 2008 Express and Windows 7. This problem occurred a week after I upgraded to SQL Server Express R2. I removed the old SQL on both machines and tested the code on the machine that is working OK. I then copied the project to the problem machine to make sure I only had one application to debug in the event of a problem later. It worked fine for about a week. Then I was contacted about the application load failure. I went in and in a desperate attempt to get them up and running, I simply created a shortcut to the debug application. I was contacted today about a another SQL connection failure. I went in and compared the services between both machines and found I had set the Logon to Local for SQL on the problem pc. I, again, reinstalled SQL and matched the service configuration to that of the other machine. I verified all services and their configurations. Now everything is the same so I think the SQL issues may be resolved.

So that only leaves this odd problem with the failure to run the release version.
Henry Minute 22-Mar-11 8:37am    
Oh well. Worth a try.

The only other thing that springs to mind, and it is almost certainly not the problem since the debug version runs, but sometimes VS gets confused about the default data connection, what with all your installing and uninstalling of SqlServer. Check under Tools|Options|Database Tools|Data Connections.

Other than that, I'm out of ideas.
TenRC 22-Mar-11 17:26pm    
Thanks Henry. I'll check into it and get back with you.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900