Dotnetpanel Forums

I've been watching the forums and trying to figure out if it's a good move or not..updating or upgrading to 1.5? I've read a couple of horror stories and still trying to determine if putting 1.5.1 within a semi-production enviroment is even realistic or just something I should wait on for the time being...

Anyone?.... I've run a test update on the update from 1.0.3 to a dev box and it just botched the applications. Anyone else had any luck with the update or are you guys recommending a complete new install.---then migrate into, I'd rather do that then risk downing the running 1.0.3 machine. not to mention the modifications i've already added ... o mi. and the updates to the clients portals.


This is gonna be fun.

I would suggest you waiting for DNP 1.5.2 including all the latest updates. DNP 1.5.2 is coming tomorrow.

Upgrade files from 1.0.3 to 1.5.0 are OK now. Anyway, we strongly recommend everybody to make backups of DNP databases and files before any upgrade. Remember, the main part of any DNP installation is Enterprise Server SQL database and Enterprise Server crypto key located in its web.config.

so I can do a complete new install for testing of 1.5.1? is this version running DNN 4.3.?

Yes, it works under DNN 4.3.1

I have got indications that 1.5.1 can't upgrade an existing 1.3 portl DB, but has to be installed into a new DB, droping all current localizations we have made for 1.3.

Will this be fixed in 1.5.2?

Are there any other localization issues/penalties upgrading from 1.3 to 1.5?

Hi century,

In order to upgrade existing 1.0.3 you just need to check "Check for updates" on the DNP installer. Also please note that update perform against all of installed components (Portal, ES, Server) not a particular one.

Steps to upgrade 1.0.3 to 1.5.1:

1. Backup all existing data (files and databases);

2. Download and run the latest DNP installer;

3. Tick "Check for updates" box and proceed with the upgrade wizard steps;

4. If any errors were appeared during installation - restore all of your files and databases back and email to our support with error log attached;

5. If update process is succeed then open portal, try to login and check whether all is ok.

6. Repeat 1 - 5 steps once until you reach desired version;

There are no any localization penalties upgrading 1.0.3 to 1.5.1, but there are some things that should be considered:

1. If you need to localize some files for your specific needs, create a copy of these files and add your culture code for them. For example: AuditLog.ascx.resx -> AuditLog.ascx.de-DE.resx, it assumes that de-DE file contains Deutch locale customizations.

2. If you had already original files localized then just add your locale code. For example: AuditLog.ascx.resx -> AuditLog.ascx.de-DE.resx, hence your locale customizations never won't be discarded with current one and future updates.

3. Please note that shared resource file (SharedResources.resx) were renamed to SharedResources.ascx.resx, thus you allowed to use DNN resource editor;

And please use the newest version of DNP Installer.

That sounds better, however I do not have the "Check for updates" checkbox/selection available in the 1.0.7 installer. The server I'm upgrading is restored and the DNP apps are installed from backups and not through the installer. If there needs to be a registry key, then it's not present.

Hi century,

You are right there is no corresponding DNP key in registry. Please find key script attached but please note that you should change all fields values that starts from '$' sign to the correct ones before exporting mentioned key in your server registry.

Super thanks Paul, however I can't access the attached file.

Thanks
/Rob

Sorry for this - please try to download once again.

Thanks Paul. 

Need some syntax checks.

[HKEY_LOCAL_MACHINE\SOFTWARE\DotNetPark\DotNetPanel\Enterprise Server]
"WebSiteId"="$website.id" - Syntax should be W3SVC1 for the Default site right?
"CryptoKey"="$cryptokey" - Should be the Machine key found in web.config (<add key="DotNetPanel.CryptoKey" value=""/>)
"InstallConnectionString"="$connection.string" - I take the complete connectionstring value from web.config (server=;database=;uid=;pwd=;)
"ConnectionString"="$connection.string" - I asume this is the same as InstallConnectionstring (Using "$connection.string")

[HKEY_LOCAL_MACHINE\SOFTWARE\DotNetPark\DotNetPanel\Portal]
"VirtualDirectory"="$virt.dir.name" - I have no virtal dir so I leave this "/"

[HKEY_LOCAL_MACHINE\SOFTWARE\DotNetPark\DotNetPanel\Server]
"Password"="$server.password" - Is this the hashed valued found in web.config of the server app or in clear text?

Thanks,
/Rob

[HKEY_LOCAL_MACHINE\SOFTWARE\DotNetPark\DotNetPanel\Enterprise Server]

"WebSiteId" - syntax should be W3SVC. For example: W3SVC/1

"CryptoKey" - correct

"InstallConnectionString" - correct

"ConnectionString" - correct

[HKEY_LOCAL_MACHINE\SOFTWARE\DotNetPark\DotNetPanel\Portal]

"VirtualDirectory" - leave empty

[HKEY_LOCAL_MACHINE\SOFTWARE\DotNetPark\DotNetPanel\Server]

"Password" - should be hashed one

Ok, then everything should be in order.

I just read that 1.5.2 is released, however as I run the Installer 1.0.7 I only have 1.5.0 as available upgrade in the dropdown box.

am I too quick or have I missed something?

Nope, you're a normal one :) In order to get running the latest DNP version you need to perform updates one by one: 1.5.0, 1.5.1 and in the end 1.5.2.