hi. might be similar problems?
first, I installed dnn 4.0.2 from the "install" package with the following steps:
- created virtual directory on my development webserver (W2K-IIS on separate machine in my LAN)
- put package contents to the real directory (<wwwroot>/dnn), set ASPNET permissions
- setup database on a second machine running SQL Server Express 2005 (SQL authentication)
- renamed/changed connection string in web.config
- ran install/install.aspx from my own machine (third one, same LAN) with fine results, especially for the module installations (ZIPs etc)
Accessing "my_website" is ok, everything's working except for the modules being "unavailable" (messages). Logging in as host or admin states always the same irrelevant stack trace string around "SQL-instance" problems. - well, after some playing around with no results, looking to help resources here and elsewhere, definitive no out-of-the-box-advice anywhere... disappointed me, I decided to use Source package instead for a fresh install.
So, I dropped & reinstalled the database, removed Install package, unzipped Source getting the library, website + solution file structure. -
When running Visual Studio 2005 from my developer's machine (LAN config as above), opening DotNetNuke.sln, I get the same error "(localhost)/DotNetNuke_2 is not installed". -
Let's say, I never wanted to install any second dnn instance on my local machine. I just wanted to have a working, clean dnn installation from scratch for either evaluation, or development purpose. -
Please, could someone point me to the right place for the appropriate information
thanks, Juergen