So we are upgrading site and came across interesting problem. We have a 6.01 version we are using upgrade path upgrades. Going to 6.4 then 7 to 8 to 9 etc etc.
So far other version 7 sites upgrade fine, the version 6 sites as stated above fails. PLEASE NOTE: We CAN navigate to the site before moving upgrade files over and login as host, move around see the site etc, meaning the web.config database connectionstring is working. However once we move files over to upgrade and the upgrade wizard requires host login, hit next, it hangs and produces the "Network related error cannot connect to sql server blaa, blaa, blaa..."
Is there another area where the connection strig for the version 6 DNN is looking when upgrading other than the web.config? It's clear it's an issue with it can't find the SQL server, no that a login is wrong...
Thank you in advance!
This is the error:
Line 213: SchedulingProvider.Instance().Halt("Stopped by Upgrade Process"); Line 214: Line 215: Upgrade.Upgrade.UpgradeDNN(strProviderPath, DataProvider.Instance().GetVersion()); Win32Exception (0x80004005): The network path was not found [SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found...
Possibly something with getting the path is wrong? string strProviderPath = DataProvider.Instance().GetProviderPath();
In case anyone else care or need this, in the DNN 6 version we had, way down in the web.config there is another "upgradeconnectionstring" that needs to match the main connection string. in our case the DNN WAS moved to a new server and the main connectionstrings were updated not the one below. All good now!
add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="Data Source=YOURSERVER;Initial Catalog=YOURDNNDB;User ID=matchtomainuser;Password=matchtomainpassword;Application Name=DNNCore;" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="" databaseOwner="dbo"
The upgradeConnectionString is not really a "strange" thing. It allows you to use a connection string with reduced permissions on the database, and a connection string with dbo permissions for the installer (also for installations of extensions afair). It is really helpful in raising the security level of your website/database access, even if it has some weak points as well, eg it has to use an SQL Server user, and the username/password credentials appear in clear text in the web.config file. But if a hacker got access to your web.config file then you have other security problems than this one... Happy DNNing! Michael
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.