issue installing via WPI

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
10/24/2009 11:21:16 AM
Gravatar
Total Posts 10

issue installing via WPI

I went through the WPI install and got hung up on creating the database due to sa not able to log in.  Weird cause I do this all day long at work...  Anyway, I am trying to find the DB install scripts in the deployment package but only find the legacy-dbscripts folder.  Is this the location for all sql script to create/install the database?

Thx

Robert

10/24/2009 11:36:32 AM
Gravatar
Total Posts 18439

Re: issue installing via WPI

If you already had SQL Express installed, most likely it was installed with configuration only for Windows Authentication and the PI wants to use sql authentication. They have made it such that if you install SQLExpress using the PI it configures it for Mixed Mode authentication which allows both Windows and Sql auth, whereas the stand alone SQLExpress installer does default to Windows only.

You can manually configure your existing installation to support Mixed Mode but then you won't know what the sa password is (it might be blank). But once configured for mixed mode you could create a new sql user named admin and add it to sysadmin role under the Security node, create a known password for this user then use it instead of sa.

Then you should be able to get the PI to work. The PI will also enforce that the dbuser for the app have a strong enough password to match the default password requirements. It needs at least 1 special char 1 upper case 1 lower case and one number so something like $Secret123 should work.

Hope it helps,

Joe

10/24/2009 11:38:24 AM
Gravatar
Total Posts 18439

Re: issue installing via WPI

Also the default is to use the .\SQLExpress instance name but if your sql installation used a default instance instead of a named instance then you need to remove that, or if you used a different instance name replace SQLExpress with your instance name.

10/24/2009 11:52:29 AM
Gravatar
Total Posts 10

Re: issue installing via WPI

My apologies, I forgot to say I am on Win7 Ultimate with SQL Server 2008 Dev Edition set to mixed mode login.  I changed the sql server user SA password and set the info in web.config for the constr.  BTW, I just went ahead and created the virtual directory in IIS7 and converted to an application, and added the IIS user to the wwwroot and gave it write permission in addition to the default.  I was able to load setup/default.aspx but obviously it said it wasnt able to connect to the db.

10/24/2009 11:56:28 AM
Gravatar
Total Posts 18439

Re: issue installing via WPI

If the file exists in the root named user.config, put your connection string there instead of Web.config, but then you need to touch Web.config to make it reload the settings. ie just type a space in it and save it. The PI would have created this file.

If the file does not exist then there must still be something wrong with the connection string you entered in Web.config.

Ideally you will use user.config for custom appSettings because then you don't lose them later when you upgrade and get a new Web.config. So if user.config does not exist open user.config.sample and save it as user.config.

Hope it helps,

Joe

10/24/2009 12:02:45 PM
Gravatar
Total Posts 10

Re: issue installing via WPI

I scratched the WPI install, doing it all manual now.  I have set the web.config to default and added the info to user.config.  I even used my administrator account in user.config and it isnt able to connect to the db.  Weird.  Researching....

10/24/2009 12:04:13 PM
Gravatar
Total Posts 18439

Re: issue installing via WPI

What is the format of your connection string? What is the exact error?

10/24/2009 12:11:38 PM
Gravatar
Total Posts 10

Re: issue installing via WPI

<add key="MSSQLConnectionString" value="server=(local)\mssqlserver;UID=mojouser;PWD=<pass>;database=mojoPortal" />

 



Welcome to mojoPortal Setup

Probing system...

File system permissions ok.

The system cannot connect to the MSSQL database. Please check your connection string.

 

System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at mojoPortal.Data.DBPortal.DatabaseHelperGetConnectionError(String overrideConnectionInfo)

10/24/2009 12:17:54 PM
Gravatar
Total Posts 18439

Re: issue installing via WPI

Are you sure your instance name is mssqlserver?

What happens if you just change it to server=localhost?

10/24/2009 1:00:42 PM
Gravatar
Total Posts 10

Re: issue installing via WPI

yes, local instance is default (mssqlserver) and it is also listed in Services as that way.  I changed user.config to locahost and reset, here is what I get.  The password has not changed and is the same as my local admin user account...



Welcome to mojoPortal Setup

Probing system...

File system permissions ok.

The system cannot connect to the MSSQL database. Please check your connection string.

 

System.Data.SqlClient.SqlException: Login failed for user 'mojouser'. at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at mojoPortal.Data.DBPortal.DatabaseHelperGetConnectionError(String overrideConnectionInfo)

10/24/2009 1:01:30 PM
Gravatar
Total Posts 10

Re: issue installing via WPI

oh, and yes it is allowed for TCP/IP connections to the server.  This is the first thing that is necessary on sql server anyway..

You must sign in to post in the forums. This thread is closed to new posts.