I receive an error that “LocalSqlServer” has already being defined. What do I do to resolve that?
A. Even though we changed the default connection string used by the ASP.NET v2.0 database driven features to “OWSqlServer”, we left the connection string called LocalSqlServer in place. This connection string does not point to a real database but is used so that developer’s local machines, with the default settings, best match the production servers. During beta testing we found that many users had “LocalSqlServer” defined in their web.config files for development but when deploying, they ran into a number of errors due to the differences between servers. To resolve this, first you must ‘remove’ the connection string which is already set in the machine.config file. Here is an example of how to remove the “LocalSqlServer” connection string in machine.config and define your own. Note that this applies to your local development the same way and is not specific to our servers.
Related Questions
- I receive an error that "LocalSqlServer" has already being defined. What do I do to resolve that?
- What general procedure a Click 2 Support technician takes to resolve the error?
- How can I resolve the unable to send authentication message error message?
- How can I resolve the unable to send authentication message error message?
- How to resolve error - Order Document Type xxxx not defined?
- How to resolve error - Order Document Type xxxx not defined?
