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...
This is the error:
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 the install.aspx.cs?
In case anyone else cares or needs 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"
Related
I have been trying to upgrade SQL server 2017 to run Python 3.7. We have installed CU28 and the product version is 14.0.3430.2 which includes the C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\PYTHON_SERVICES.3.7.
I have made sure all permissions are granted to the INSTANCENAME directory and pythonlauncher.config working directory is pointing to C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\MSSQL\ExtensibilityData and launchpad service account has permissions to this directory.
I have done all this as an upgrade twice and got various errors, and a clean install. The error I am getting is
Msg 39004, Level 16, State 20, Line 0
A 'Python' script error occurred during execution of 'sp_execute_external_script' with HRESULT 0x80004004.
Msg 39019, Level 16, State 2, Line 0
An external script error occurred:
Invalid BXL stream
error while running BxlServer: caught exception: Error communicating between BxlServer and client: 0x000000e8
HRESULT 0x000000e8 looks like INVALID_CANCEL_OF_FILE_OPEN
HRESULT 0x80004004 looks like E_ABORT
So no real clues what is wrong here. pythonlauncher.log does show the error;
[Error] Process::TryTerminate failed with error code: 5
Session 0E93E9D1-07A7-448A-8B1A-FCA5263A5F53 TryTerminate(1067) failed with 5
Error code 5 is ERROR_ACCESS_DENIED
Also got this warning
[Warning] StaleDirectoryCleaner() failed to delete C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\MSSQL\ExtensibilityData\FAMSQL17UAT01\8B97815A-E9EA-4FA0-98F3-0440D4180522 after 5 retries
So all up this looks there are still permission issues. Extremely frustrating as there is next to no help on this. Any help would be greatly appreciated.
UPDATE:
After another clean install - first checked Python 3.5.2 worked and it did. Upgraded to 3.7, and again got the same issue. A bit more digging around I find this...
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SERVERNAME.domain_name.com:INSTANCENAME ]
Login failed for user 'DOMAIN\SERVERNAME$'. Reason: Could not find a login matching the name provided.
We have a service account that is not part of the domain which is NT Service\MSSQL$INSTANCENAME. Why on this implementation expecting a windows authenticated user the same name as the server??? How can I go about remedy this?
I think what has happened is that MS have left debug code in their production release.
FURTHER UPDATE:
In the event log we are seeing
Faulting application:Python.exe: 3.7.1150.1013 Faulting module name:
pylink.pyd Faulting module path:c:\Program Files\Microsoft SQL
Server\MSSQL14.INSTANCENAME\PYTHON_SERVICES.3.7\lib\site-packages\revoscalepy\rxLibs\pylink.pyd
Microsoft have confirmed that this is a bug. Their work around is below.
It's CU27 and CU28 that 3.7 is broken in - so you could use CU26 and still use Python 3.7. That version started at CU22... so CU22-26 work fine.
Or - it's only the pylink.pyd that is broken - you can simply grab the pylink.pyd from a CU22-26 installation for Python 3.7, and swap it into your CU27/CU28 files. This workaround will work now, and will also not cause any issues going forward once the fix does come. That is, on your next update, it shouldn't interfere and it should all go smoothly.
i tried to use owncloud but i cannot access to my server (localhost/database is not found). I realized apache 2 is not working currently. I got this errors :
How can i fix this problem ? Have a good day
As written in the error message, there seems to be no /var/log/apache2 directory or it is not writeable for the user running your apache daemon.
I'm having a problem upgrading a site from CMS 6 R2 to 7. I'm getting a wait timeout error while upgrading using the Deployment Center.
I already tried to add the following configuration in C:\Program Files (x86)\EPiServer\Shared\Install\EPiServerInstall.exe.config:
<appSettings>
<add key="commandTimeout" value="600"/>
</appSettings>
but no avail.
As much as I don't want to resort to manual upgrade, is there a way to override the connection timeout?
Thanks in advance for any help.
Edit:
Upgrade log (too long so I cut it just to display the error message):
....
Executing database script "C:\Program Files (x86)\EPiServer\CMS\7.0.586.1\Upgrade\Database\sql\0007_0000_0041_0000to0007_0000_0147_0000.sql"
An error has occured and the transaction will be rolled back
Rolledback
The wait operation timed out
The wait operation timed out
An unhandled error has occured:
The wait operation timed out
When executing
At C:\Program Files (x86)\EPiServer\CMS\7.0.586.1\Upgrade\System Scripts\Upgrad
e Site Database (SqlServer).ps1:9 char:2
+ Execute-EPiSqlSvrScript -EPiServerScript -ScriptPath $file -SqlServerName
$dbCo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~
=
Get-EPiIsBulkInstalling
At C:\Program Files (x86)\EPiServer\CMS\7.0.586.1\Upgrade\System Scripts\Upgrade Site Database (SqlServer).ps1:9 char:2
+ Execute-EPiSqlSvrScript -EPiServerScript -ScriptPath $file -SqlServerName $dbCo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at EPiServer.Install.InstallationManager.Install(Installer installer)
at EPiServer.Install.SqlServer.SqlServerInstallationManager.ExecuteDatabaseScript(String sqlServerName, Nullable`1 sqlServerPort, String databaseName, String loginName, String loginPassword, String scriptFilePath, Boolean avoidDbTransaction, Boolean isEPiServerScript, IDictionary parameters)
at EPiServer.Install.SqlServer.Cmdlets.ExecuteSqlScriptCmdlet.ProcessRecord()
at System.Management.Automation.Cmdlet.DoProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
If I am not mistaken (been a while since I used Deployment Center) it uses the connectionstring from web.config for the site and in that you can define timeout.
See example here: https://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectiontimeout%28v=vs.110%29.aspx
I restarted the site then refreshed the site in DC and it worked now. Looks like the settings are cached in DC.
I migrated an old site to a new one and I am trying to rename the old site to legacy.domainname.com
Here is what I have done:
In Linode DNS Manager, I made the necessary DNS updates and the new site is up
For the legacy site
I changed every instance of www.domainname.com to legacy.domainname.com
I made these changes in
/etc/apache2/sites-enabled and
/etc/apache2/sites-available
Now I am trying to restart apache2 and it is giving one error after the other, all the errors are like this
apache2: Syntax error on line 235 of /etc/apache2/apache2.conf: Syntax error on line 30 of /etc/apache2/sites-enabled/legacy.domainname.com.conf/assets/images/3310sm.jpg: Expected </xapMM:DocumentID>adobe:docid:photoshop:37b23e53-24f1-11dc-83c5-ba417a2e0e5f</xapMM:DocumentID> but saw </rdf:Description>
or this
apache2: Syntax error on line 235 of /etc/apache2/apache2.conf: Syntax error on line 30 of /etc/apache2/sites-enabled/legacy.txsystems.com.conf/TestFolder/form.phtml_not_needed: Expected </h1><?php> but saw </div>
if I remove the referenced file, it will jump to a next thing, now these are files that have worked for 10 years, nothing changed. All I want is to change the domain to legacy
Please can you help point towards a possible troubleshooting step
All I want to run is sudo /etc/init.d/apache2 start
I solve the problem by
Restoring the server from last good backup so I remove my changes
Then I edit /etc/apache2/sites-enabled/www.domainname.com.conf and change
ServerName from www.domainname.com to legacy.domainname.com
Restart apache (/etc/init.d/apache2 restart)
And that is it
Thanks
I am trying to install dotnetnuke in my system. For that i have unzipped dotnetnuke installable zip at C:\inetpub\wwwroot\DotNetNuke and created this directory as virtual in iis. Any other than this i have to do to successfully install ddn. How to create and attach database with it. Currently i am gettting below error.
Server Error
HTTP Error 500.19 - Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code: 0x80070021
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost:80/dotnetnuke
Physical Path: C:\inetpub\wwwroot\DotNetNuke
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File: \?\C:\inetpub\wwwroot\DotNetNuke\web.config
Config Source:
79:
80:
81:
More Information... This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
Server Version Information: Internet Information Services 7.0.
Microsoft has a tool called Webmatrix which makes it very easy to install DotNetNuke (and other applications).