DotNetNuke Upgrade 4.9.2 - PermanentRedirect Failure - dotnetnuke

When installing DNN 04.09.02 upgrade (from DNN 4.8.4) I receive System.IndexOutOfRangeException: PermanentRedirect error and cannot install the upgrade. How do I get around this so I can install the upgrade?

This thread might help you:
It looks like you have to update it manually... steps are described there.
Also check this thread, might be due to AD if AD is used.

I've re-posted the following from the thread provided by kitsune. Source
First try the following in your browser. Replace "www.yourdomain.com" with your domain:
http://www.yourdomain.com/install/install.aspx?mode=install
If that doesn't work (which it didn't for me) then try the following steps (copied from Chris on that thread).
To manually run the SQL portion of the upgrade you'll need to run each upgrade script between your version and 4.9.2. I upgraded from 4.9.0 to 4.9.2 so I performed the following:
On the web server open the directory: \Providers\DataProviders\SqlDataProvider
Determine which files need to be run. Basically, all of the versions after your old version. In my case I needed to run the files 04.09.00.SqlDataProvider, 04.09.01.SqlDataProvider and 04.09.02.SqlDataProvider.
Open the SQL files in a text editor and replace "{databaseOwner}" (usually with "dbo.") and "{objectQualifier}" (usually with "", but sometimes "DNN4" or some other object prefix)
Run those SQL files in version order using SQL Management Studio.
Assuming those scripts ran without an error then the site should be ready to use.

Related

Could not Load timescaledb-1.6.0.dll - Not a Valid Win32 Application

I've come across an issue when attempting to load timescaledb using PostgreSQL v10.11... Upon executing the following command:
CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;
I'm greeted with the following error:
ERROR: could not load library "<postgresfolder>/lib/timescaledb-1.6.0.dll": %1 is not a valid Win32 application.
postgresfolder = The path to my postgres installation location.
I've attempted this with PostgreSQL v11.6 aswell, with the same outcome. I don't believe it to be a dependency issue (Visual Studio C++ Redist. 2015) as I meet all the prerequisites listed # https://docs.timescale.com/latest/getting-started/installation/windows/installation-windows.
Any help would be greatly appreciated!
(EDIT): The installation is being performed on Windows 10, 64bit.
I got this problem due to ssleay32 and libeay32 dlls. Get binaries from https://get.enterprisedb.com/postgresql/postgresql-11.4-1-windows-x64-binaries.zip and copy them from postgresql-11.4-1-windows-x64-binaries/bin into your /bin folder. If they did not exist, still copy and keep them there.
Also, it looks like timescaledb only works with 11.4 version if you wanna stick with 11.

Unable to find an entry point named 'Environment_SetEnv' in DLL 'Magick.NET-Q8-x64.Native.dll'

Upgraded to latest ImageMagick / Magick.NET (7.0.2.901), and it built and ran fine locally, but explodes on the server with this error.
Unable to find an entry point named 'Environment_SetEnv' in DLL 'Magick.NET-Q8-x64.Native.dll'.
Seems to be a new issue. Judging by the change desc here:
https://magick.codeplex.com/discussions/650746
The VC Runtimes are no longer required, so installing them wouldn't be the issue - and, I've installed 2008, 2012 and 2015 VC runtimes for prior versions of the library, which worked fine.
Windows Server 2008 64-bit, 64-bit .Net 4 in IIS.
Current workaround is to roll back to 7.0.0.22, which runs without error.
Install-Package Magick.NET-Q8-AnyCPU -Version 7.0.0.22
I had this issue a couple months back and eventually found two separate causes:
AnyCPU Conflict with Previous Versions
Problem: Magick.NET caches the native library in a temp directory unless it already exists (Relevant source code). Since I had previously tested with the Q8-x64 version (which doesn't test for CPU architecture), the Magick.NET-Q8-x64.Native.dll already existed and was not overwritten.
Resolution: Delete the native library's temp directory. On my version of Windows, it was located at %TEMP%\Magick.NET.{TargetFramework}.{MagickNETVersion}. The Q8-AnyCPU version then extracted a new native library with the Environment_SetEnv method.
Lack of Permissions in Cache Directory
Problem: The native library was cached in a directory with restricted permissions for executing code.
Resolution: Change the cache directory's location. My solution is the following code.
#if DEBUG
private static bool MagickCacheDirectoryIsSet = false;
public DefaultConstructor()
{
if (!MagickCacheDirectoryIsSet)
{
ImageMagick.MagickAnyCPU.CacheDirectory = #"path\to\more\permissive\directory";
MagickCacheDirectoryIsSet = true;
}
}
#endif
Follow these steps:
Go to NuGet package manager for the solution (not the project)
Uninstall any previous versions of Magick.net
Install new version of Magick.net to desired projects
Go to the bin folder of the main project and delete any magick.net file
Run your solution
I successfully tested this method on VS2017 and Magick.net 7.6.1 (previous installation was 7.4.4)
Had the same issue, deleting the all magick dlls from the bin folder and reinstall solved it.

Microsoft's Node.JS driver does not work

I tried following this but with no luck.
http://blogs.msdn.com/b/sqlphp/archive/2012/06/08/introducing-the-microsoft-driver-for-node-js-for-sql-server.aspx
Every time I try to build it, it fails.
Does anyone have any ideas as to why does it fail to build. I am also using the latest version of Node if that helps.
Thanks for your question. Just to clarify you are using the msnodesql driver right?
One of the reasons that you might not be able to build is because you are using the latest node version.
The Microsoft Node.js driver is not forward compatible. The next version is in the pipeline. In the meanwhile you will have to downgrade your node.js version to 0.8.9.
Additionally there are a few other requirements. Follow these steps and you should be good.
Node.js – Version 0.8.9 (32 bit version). Make sure you download the x86 version and not the x64 version. You might have to uninstall your current version and re-install this version to ensure compatibility.
Python 2.7.6.
Visual C++ 2010 - the Express edition is freely available from Microsoft.
SQL Server Native Client 11.0 - available as Microsoft SQL Server 2012 Native Client found in the SQL Server 2012 Feature Pack.
Then just enter these in your node.js command prompt
1. npm install msnodesql
2. npm install -g node-gyp
3. node-gyp configure
4. node-gyp build
You should now see a build folder inside msnodel.
Navigate to build > release. Copy the sqlserver.node file and paste it in the msnodesql > lib folder. Replace the old file if needed.
Now you can follow the rest of the instructions on the blog you mentioned which will help you with connection string and connecting to your db. Let me know if you are still stuck.
Thanks

Which sonar-maven-plugin version to use?

I am wondering which sonar-maven-plugin in which version I should use.
As far as I know there is a org.codehaus.mojo version and two org.codehaus.sonar versions (sonar-maven3-plugin, sonar-maven-plugin).
As far as I understand the sonar-maven3-plugin is now deprecated and the org.codehaus.sonar:sonar-maven-plugin should be used instead. However those org.codehaus.sonar version are tied to a certain version of the sonar server, therefore it makes probably no sense to use them directly.
To be able to deal with this there is the org.codehaus.mojo:sonar-maven-plugin which checks which sonar version the server has and from there checks which org.codehaus.sonar:sonar-maven-plugin to use.
So in order to have a maven pom that is independent of the Sonar Server Version one should probably use the org.sonar.mojo:sonar-maven-plugin:RELEASE version to be safe.
Did I get this right?
Any further things to consider?
Thanks
As described in the documentation page (see "Project analyzed with Maven 3"), the plugin you have to use is org.codehaus.mojo:sonar-maven-plugin, not the internal one(s).
When we were using sonarserver ver 3.7.1 we used to have org.codehaus.sonar:sonar-maven-plugin.
Once we migrated from Sonar Server to SonarQube server 4.5+ onwards, we need to use org.codehaus.mojo:sonar-maven-plugin.
Currently in our project , we need to compile our code with jdk 6(as it is old project) and run the sonarqube server ver 4.5.7 analysis with java 7
so with java 6 we run the command mvn clean org.jacoco:jacoco-maven-plugin:0.7.4.201502262128:prepare-agent install and while running the sonar analysis we change the jvm to java 7 and execute the command mvn org.codehaus.mojo:sonar-maven-plugin:2.4:sonar -Dsonar -Dsonar.host.url=http://localhost:9000 -Dsonar.dynamicAnalysis=true

Installing MDS Excel Add-In Issue with Prerequisites

I am attempting to install the Master Data Services Plugin for Excel, but can't get the install to actually process due to it saying the prerequisites are not installed:
I have made sure I have the right version (32 bit) to match my version of excel (2010), and have the full version of .net 4.5 installed. If I try to install the full version of .net 4.0, I am told that the newer (4.5) version already is installed.
Here are some links with similar issues, but no response:
Microsoft Answers; Microsoft Connect;
Has anyone else faced this issue and got around it?
So, this looks to be a simple fix. The installer needs to be run as administrator, but in order to do that you have to run it through the command prompt as administrator. After doing this, it installed ok.
I'm not sure why the installer didn't request elevated privileges, but I'm guessing it couldn't properly query the system to verify the necessary prerequisites were installed.
Hopefully this helps someone else in the future!

Resources