SQL Connection dropping
-
I have a series of strongly typed datasets in my .NET v2 project. When I shift the project to .NET v3.5 the system runs the first connection but refuses any further connections giving me a Named Pipes error... I thought that there were no code changes required to migrate from v2 to v3.5, well obviously there should have been because it no longer works, but what should I be looking for? Any ideas? Thanks
-
I have a series of strongly typed datasets in my .NET v2 project. When I shift the project to .NET v3.5 the system runs the first connection but refuses any further connections giving me a Named Pipes error... I thought that there were no code changes required to migrate from v2 to v3.5, well obviously there should have been because it no longer works, but what should I be looking for? Any ideas? Thanks
Make sure your connections are properly released. Also, make sure that your application accesses the database in a linear manner. Then make sure that SQL server is properly configured, etc. Your error, unfortunately, has many potential causes. The current project I am working can be built in 2.0 or 3.5 and access the database without an error so it can happen seamlessly depending on your code.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
I have a series of strongly typed datasets in my .NET v2 project. When I shift the project to .NET v3.5 the system runs the first connection but refuses any further connections giving me a Named Pipes error... I thought that there were no code changes required to migrate from v2 to v3.5, well obviously there should have been because it no longer works, but what should I be looking for? Any ideas? Thanks
There must not be any code changes while migrating from 2.0 to 3.5 as framework core(structure) remains the same retaining all previous functionality. All the enchancements are additional to the 2.0.