We'r sorry . The following components have failed to install.

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.
9/9/2009 4:41:09 AM
Gravatar
Total Posts 3

We'r sorry . The following components have failed to install.

Hello ,

Am new to this concept. Am facing problem while installing Web Platform Installer 2.0 RC.Could you help me out.

My system : Windows XP Professional version 2002 Service Pack 2

Database :  SQL SERVER 2005

Mojoportal : recent released version available at download option.

Am getting the below error:

We'r sorry . The following components have failed to install.

  mojoPortal

     This product did not install successfully . the database 'mojoportal' could not be created.

View log:

[14:50:15]The database 'mojoportal' could not be created.. Retrying operation 'Add' on object dbFullSql (data source=.\SQLExpress;initial catalog=mojoportal;user id=sa). Attempt 1 of 5.

Details:

originalMessage: The database 'mojoportal' could not be created.

operationType: Add

retryAttempt: 1

retryCount: 5

[14:50:15]The database 'mojoportal' could not be created.. Retrying operation 'Add' on object dbFullSql (data source=.\SQLExpress;initial catalog=mojoportal;user id=sa). Attempt 2 of 5.

Details:

originalMessage: The database 'mojoportal' could not be created.

operationType: Add

retryAttempt: 2

retryCount: 5

[14:50:15]The database 'mojoportal' could not be created.. Retrying operation 'Add' on object dbFullSql (data source=.\SQLExpress;initial catalog=mojoportal;user id=sa). Attempt 3 of 5.

Details:

originalMessage: The database 'mojoportal' could not be created.

operationType: Add

retryAttempt: 3

retryCount: 5

[14:50:15]The database 'mojoportal' could not be created.. Retrying operation 'Add' on object dbFullSql (data source=.\SQLExpress;initial catalog=mojoportal;user id=sa). Attempt 4 of 5.

Details:

originalMessage: The database 'mojoportal' could not be created.

operationType: Add

retryAttempt: 4

retryCount: 5

[14:50:31]The database 'mojoportal' could not be created.. Retrying operation 'Add' on object dbFullSql (data source=.\SQLExpress;initial catalog=mojoportal;user id=sa). Attempt 5 of 5.

Details:

originalMessage: The database 'mojoportal' could not be created.

operationType: Add

retryAttempt: 5

retryCount: 5

EXCEPTION: Microsoft.Web.Deployment.DeploymentException: The database 'mojoportal' could not be created. ---> System.Data.SqlClient.SqlException: Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection.

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)

at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)

at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)

at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

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 Microsoft.Web.Deployment.SqlDatabaseProvider.AddHelper(DeploymentObject source)

--- End of inner exception stack trace ---

at Microsoft.Web.Deployment.DeploymentObject.Add(DeploymentObject source, DeploymentSyncContext syncContext)

at Microsoft.Web.Deployment.DeploymentSyncContext.HandleUpdate(DeploymentObject destObject, DeploymentObject sourceObject)

at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildrenOrder(DeploymentObject dest, DeploymentObject source)

at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildren(DeploymentObject dest, DeploymentObject source)

at Microsoft.Web.Deployment.DeploymentSyncContext.ProcessSync(DeploymentObject destinationObject, DeploymentObject sourceObject)

at Microsoft.Web.Deployment.DeploymentObject.SyncToInternal(DeploymentObject destObject, DeploymentSyncOptions syncOptions, PayloadTable payloadTable, ContentRootTable contentRootTable)

at Microsoft.Web.Deployment.DeploymentObject.SyncTo(DeploymentProviderOptions providerOptions, DeploymentBaseOptions baseOptions, DeploymentSyncOptions syncOptions)

at Microsoft.Web.Deployment.DeploymentObject.SyncTo(String provider, String path, DeploymentBaseOptions baseOptions, DeploymentSyncOptions syncOptions)

at Microsoft.Web.Deployment.DeploymentObject.SyncTo(DeploymentWellKnownProvider provider, String path, DeploymentBaseOptions baseOptions, DeploymentSyncOptions syncOptions)

at Microsoft.Web.Deployment.DeploymentObject.SyncTo(DeploymentBaseOptions baseOptions, DeploymentSyncOptions syncOptions)

at Microsoft.Web.PlatformInstaller.MsDeployProxy.Install(InstallerItemInstallContext context, RemoteCredentials remoteCredentials)

 

Thank you

9/9/2009 6:42:50 AM
Gravatar
Total Posts 18439

Re: We'r sorry . The following components have failed to install.

Hi,

The most likely problem is if your SQLExpress is only configured for Windows Authentication. It needs to be configured for Mixed Mode to allow using a sql user like sa in the connection string. Are you sure the sa account works? Are you able to connect using the sa user using SQL Management Studio? Are you sure of the sa password?

If its not currently configured for Mixed Mode then configure it for that and create a new sql user named admin and gicve it a password then add it to the sysadmin server role under the sql security node.

Are you sure your SQL 2005 is a named instance or a default instance. For an instance named "SQLExpress" which is what is typical with a default instalation of SQL Express then the connection string needs the instance name like localhost\SQLExpress, else if its a default instance it only needs the localhost part

Else you can install it manually and create your own db and set your own connection string.

Hope it helps,

Joe

9/10/2009 1:09:29 AM
Gravatar
Total Posts 3

Re: We'r sorry . The following components have failed to install.

Hello Joe,

  Thanks for the response. Am using Mixed mode with sa connections. Infact I reinstalled my SQL 2005 with mixed mode. And SQL 2005 is in name instance like  localhost\SQLExpress. Have tried to install mojoportal. Yet am facing same problem as " We'r sorry . The following components have failed to install". " The database 'mojoportal' could not be created."

Thank you.

 

 

 

 

 

9/10/2009 1:12:25 AM
Gravatar
Total Posts 3

Re: We'r sorry . The following components have failed to install.

Hello Joe,

   Now its working. I tried creating a new database. It got installed successfully. Thank you for the response. 

Apeksha..

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