Last post Sep 21, 2005 06:56 AM by email@example.com
Aug 24, 2005 12:15 AM|martin4995|LINK
Sep 08, 2005 09:23 AM|pietje_puk100|LINK
I suffer the same problem. Although my site is running on a XP system together with a MSDE 2000 SP4.
I first got an other error which goes like this:
Format of the initialization string does not conform to specification starting at index 61
When i reenter the internet adress of my local dnn-site i get the same error like you.
Do you already have a way arround this?
Sep 08, 2005 05:07 PM|mcadams|LINK
Has the same problem. The only way was to make the DotNetNuke to install as a fresh copy not an upgrade.
In order to do this you need to stop IIS server. Go to C:\WIN\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\ and remove the whole directory DotNetNuke.
After starting IIS and running the installation once again it should go without problems.
The directory with nuke should be placed under wwwroot in IIS directory. The ASPNET user should probably have full access rights for entire nuke folder including subfolders.
Sep 08, 2005 05:34 PMfirstname.lastname@example.org|LINK
SQL Server does not exist or access denied.
In Win2000 Server there is not an ASP Net user available to add to the permission properties for the directory "c:\dotnetnuke". Anyone have any ideas?
Sep 09, 2005 05:25 AM|pietje_puk100|LINK
Sep 20, 2005 03:48 PM|stevepowell|LINK
Sep 21, 2005 06:56 AMemail@example.com|LINK
The DotNetNuke files can be placed anywhere. You then need to create a virtual folder in IIS pointing to the DNN folder, and set that as an application root. That's true of any ASP.NET app. There is also an issue with permissions if DNN is immediately
under the root of a drive. The account accessing DNN must have file scan rights to the root of the drive.