Last post Feb 11, 2006 01:28 PM by DeveloperMCDBA
Nov 28, 2004 05:38 AM|cyrixxs|LINK
Feb 11, 2006 04:34 AM|DeveloperMCDBA|LINK
I've having this same problem with a 3.2.0 install. I'm testing my modules against a multiple object qualifier setup to make sure it works ok, however, at the moment, I can't get a 2nd portal setup that uses the object qualifier.
Portal #1, set the connection string in web.config, then set the object qualifier in the web.config:
Portal #2, set the cnn str to be the same, then set the object qualifier in the web.config to be different...
the 2nd one installs ok, but when I "click here to go to portal" I get that error?
I've looked in the official documentaion for this, and I didn't see anything.
Feb 11, 2006 12:39 PM|DeveloperMCDBA|LINK
I did find this:
Try changing the web.config file. There is a key named <add key=”InstallMemberRole” value=”true” />, change it to
<add key=”InstallMemberRole” value=”false” />. This, according the DNN documentation, will make the install process not to run the member role scripts.
Feb 11, 2006 01:28 PM|DeveloperMCDBA|LINK
Did that, still get this error:
00:00:19.548 - Executing Additional Scripts:
00:00:19.548 - Creating Portal: My Website
00:00:20.779 - Error: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_DNN3202_TabPermission_DNN3202_Permission". The conflict occurred in database "DotNetNuke03", table "dbo.DNN3202_Permission", column 'PermissionID'. The statement has
00:00:20.779 - Portal failed to install:
00:00:20.779 - Installing Optional Resources:
Portal still doesn't come up.
Any advice appreciated. [:)]