This is a long question, but please bear with me.

I have an error message when trying to populate the database.

Here is the error message I get when I browse to http://localhost/dotnetnuke in order to get the scripts going to populate the database:

-----------------------------------------------------------------------------------
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'DotNetNuke.Global'.

Source Error:

Line 1: <%@ Application Codebehind="Global.asax.vb" Inherits="DotNetNuke.Global" %>


Source File: C:\Inetpub\wwwroot\dotnetnuke\global.asax Line: 1
------------------------------------------------------------------------------------
Setup on my local machine:

Windows XP Professional
SQL Sever 2000
VisualBasic.net
Ibuyspyportal installed and still works when I bring it up in Visual Studio
Asp.net 1.0


Here is what I did to install DNN.

1) Made a directory c:\inetpub\wwwroot\dotnetnuke
2) Set permissions (read, write, scripts, etc)
3) Created vrirtual directory with alias dotnetnukevirtual (because system said that dotnetnuke was already used. I don't know how it was already used).
4) Created database called dotnetnuke.

I made the following two changes to the web config file before installation.

1) Changed connection string to the following:

<add key="connectionString" value="Server=localhost;Trusted_Connection=true;Database=dotnetnuke" />

My IBS portal uses this Trusted_connection feature when accessing the database on my local machine. I do not know if I have a database password set up in SQL Server on my local machine (someone helped me establish the IBS portal a year ago).

2) I commented out all of the references to the Mobile devise. Why? Because I kept getting an error message related to Mobile controls. I had the same problem when installing IBS and Commenting out the references to the mobile controls fixed it.

Here is what the config file looks like now:

<configuration>
<!-- application specific settings -->
<appSettings>
<add key="connectionString" value="Server=localhost;Trusted_Connection=true;Database=dotnetnuke" />
<!-- database connection details -->
</appSettings>
<system.web>
<httpModules>
<add name="HTTPHandler" type="DotNetNuke.HTTPHandler, DotNetNuke" />
</httpModules>
<!-- set debugmode to false for running application -->
<compilation debug="true" />
<!-- permits errors to be displayed for remote clients -->
<customErrors mode="RemoteOnly" />
<!-- Forms or Windows authentication -->
<authentication mode="Forms">
<forms name=".DOTNETNUKE" protection="All" timeout="60" />
</authentication>
<!--
<authentication mode="Windows">
<identity impersonate="true"/>
</authentication>
-->
<!-- allow large file uploads -->
<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" />
<!-- Adapter configuration for mobile controls used in the portal -->
<!-- mobileControls>
<device name="PortalHtmlDeviceAdapters" inheritsFrom="HtmlDeviceAdapters">
<control name="DotNetNuke.MobileControls.TabbedPanel, DotNetNuke" adapter="DotNetNuke.MobileControls.HtmlTabbedPanelAdapter,DotNetNuke" />
<control name="DotNetNuke.MobileControls.LinkCommand, DotNetNuke" adapter="DotNetNuke.MobileControls.HtmlLinkCommandAdapter,DotNetNuke" />
</device>
<device name="PortalChtmlDeviceAdapters" inheritsFrom="ChtmlDeviceAdapters">
<control name="DotNetNuke.MobileControls.TabbedPanel, DotNetNuke" adapter="DotNetNuke.MobileControls.ChtmlTabbedPanelAdapter,DotNetNuke" />
</device>
<device name="PortalWmlDeviceAdapters" inheritsFrom="WmlDeviceAdapters">
<control name="DotNetNuke.MobileControls.TabbedPanel, DotNetNuke" adapter="DotNetNuke.MobileControls.WmlTabbedPanelAdapter,DotNetNuke" />
</device>
</mobileControls-->
<!-- Mobile device filters used for customizing portal -->
<!--deviceFilters>
<filter name="isJScript" compare="javascript" argument="true" />
<filter name="isPocketIE" compare="browser" argument="Pocket IE" />
<filter name="isHTML32" compare="preferredRenderingType" argument="html32" />
</deviceFilters -->
<pages enableViewStateMac="true" />
</system.web>
</configuration>



Thanks,

Steve

Steve,

First of all DotNetNuke like to be on your drive like c:/ and using c:\inetpub\wwwroot\dotnetnuke may be causing file location problems.
Follow the instructions in the Readme.txt file and they will clarfiy some of what's below.

Second, permissions for the local path section in IIS only need read to work and set Execute Permissions: below to scripts only.

Third, you may want to go into IIS and remove the DotNetNuke (if it is there) and your dotnetnukevirtual you created and create the new DotNetNuke one once again.
This will make it easier to follow everyones steps or directions down the road.

Fourth, a stock standard web config connection string should look like this: (taken from 1.0.10)
<add key="connectionString" value="Server=localhost;Database=DotNetNuke;uid=sa;pwd=;" />
Try replacing this with the one you have. You don't need the trusted stuff.

The errors relating to the mobile devices are for the Mobile Internet Toolkit which must be installed. You still may get an error message even though you have this installed but if you ignore this and say okay (if I remember right) and continue on it will install through this.

Fifth, you may want to change the line <customErrors mode="RemoteOnly" /> to say
<customErrors mode="OFF" /> instead to show error messages while debugging. (OFF is case sensitive)


Give it another go and good luck...

Tom

---

http://www.dnnfaq.com

http://www.websplus.net

http://www.sdarchery.com

Steve,
I almost forgot try going to this site http://dotnetvet.net/duh/ as he has a "how to do" for a clean install that will help you out.

duhdotnetnuke

Tom

---

http://www.dnnfaq.com

http://www.websplus.net

http://www.sdarchery.com

Hi,

Thanks for your reply. I did what you suggested. I put DNN in c:\dotnetnuke and then I eliminated the "dotnetnukevirtual" virtual directory that I had created before.

I then extracted the files to C:\dotnetnuke. I also did not modify the config file so that I avoided using the trusted connection statement that I had in there before.

When I ran http:\\localhost\dotnetnuke I still got the mobile controls error and again I just commented them out (no more error message).

I then got the following error message:

---------------------------------------
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[SqlException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.]
System.Data.SqlClient.SqlConnection.Open() +761
DotNetNuke.AdminDB.ExecuteSQLScript(String strScript)
DotNetNuke.Global.Application_Start(Object Sender, EventArgs E)

--------------------------------------------------------------------------------

I am not very familiar with Sql server security. I did not put a user name and password in the connection string, i just left them blank.

Any help that you guys could give me would be appreciated.

Thanks,

Steve

Steve,

The connection string that Tom gave you will only work if you set up the server with the SA user having a null password. Try one of two things:

1) Make sure the ASP.NET user in the database has the Database Owner role in the DotNetNuke database and try your trusted connection string again.

2) Set up a user in the DotNetNuke database and give that user the Database Owner role in the DotNetNuke database. Then change the connection string in web.config to <add key="connectionString" value="Server=localhost;Database=DotNetNuke;uid=;pwd=;" />, where UID is the username of the user you set up in the database and pwd is that user's password.

If you are getting a login error, you probably have the application set up correctly. Now if you fix the SQL database login problem you should be good to go.

I hope this helps you. Keep us updated!

---

Jeremy

Thanks,

That is a big help.

I have two related questions.

1) Under option one (above) who is the ASP.net user? I created the database, so am I the ASP.net user? I have IBS portal working under another database, does it have a separate password set up?

2) If I choose to set up a user name and password, am I going to have a problem later when I upload the database (using DTS) to the web hosts' server since they will give me different passwords for the database on their server?

Thanks again,

Steve

Steve,

1) If you are already using a trusted connection for your IBS database, then under "Security">"Login" in Enterprise Manager, there should be a list of usernames. ASPNET should be one of them, assuming this is the machine account used to start the ASP.Net processes. This is the user I am referring to. You need to add this user to the DotNetNuke database and make him a database owner.

2) When you upload to the server (DTS), then you will need to change you web.config file to reflect the username and password your webhost will give you. When the webhost sets this database and user up, they should give the user the Database Owner role.

Let me know if you have more questions.

---

Jeremy

Steve and Jeremy,

First thing the connection string I showed Steve was the stock string from a fresh copy of 1.0.10 to show him the format and I should have explained more to him, my fault.

For my IBS or DNN portals I have never used that trusted connection stuff. I use SQL Enterprise Manager to create my database, username and password.

Then I alter the web config to match these and open the site to let it run the sql database scripts and have never had a problem.

My string will look like this: (I bolded the parts to be changed as required)
<add key="connectionString" value="Server=localhost or servername;Database=DotNetNuke or other name;uid=enter name;pwd=;enter name" />,

Once the site is moved to a production site I change these to match my host setup info.

I can run DTS to transfer data to my host sql with no problems. The main thing is what ever user you are using is set as the database dbo and all else should be fine.
When the sql install script runs the first time it has lines like: CREATE TABLE [dbo].[Announcements] where it builds tables and stored procedures for the dbo, thus why the user needs to be set as dbo.

I have never had to mess with the ASPNET user, but I am assuming this is because I have Visual Studio .Net installed and it did it for me.

Thanks
Tom

---

http://www.dnnfaq.com

http://www.websplus.net

http://www.sdarchery.com

Thanks guys,

I used the first method. Gave the ASPNET user public and DB owner permissions and used trusted connection in the connection string.

IT WORKED!

The database was populated and everything is set to go. This has been a lot easier then the original IBS portal for me.

Thanks a lot for your help.

Steve