Hello we are migrating CuteLiveSupport 4.1.0.0 from IIS 6 Windows 2003 to IIS 7 Windows 2008 server. Copied all files from old IIS site to new one. Created new database and restored 2003 database to new SQL 2005 database. Using the same connection string and setup current SQL user as dbo on new database. The user that is used to connect to the database with connection string can be used in SQL Mgt Studio to open and edit all tables and is set as the dbo.
Do you have upgarde documentation for Verison 5 can't seem to find directions of what the procedures for upgrading is.
Here is the connection string we are using for IIS 7 in App Settings: Data Source="IPAdddress",2433;Initial Catalog=cutechat;Persist Security Info=True;User ID="SQLUser";Password="SQLUserPassword";
The string format funtions fine from SQL Mgr and other apps on the same IIS server. Is it possible the app does not understand the port connection parameter that is the only parameter that had to be changed in the migration?
We receive the following error when tring to login the the chatLiveSupport site:
The ConnectionString property has not been initialized.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: The ConnectionString property has not been initialized.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. |
I'm not sure why this occurs. Should I reinstall the app and restore the database after we initilaize the database?