MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Install Error, current version 4_5_3057_40 (Closed) (Mono Support )

Viewed 101190 time(s), 23 post(s) 10/23/2011 2:31:47 AMby Kiamori
khorvat

khorvat

10/24/2011 8:47:35 PM
Hi,

I didn't noticed at first that you didn't mentioned any errors while running create database script. If you did run a script on an empty database without an error then everything should be ok, and you should either use installer or set everything manually to get the MonoX working (SQL connection string and InstallationDone AppSetting).

Please let us know how you would like to proceed, via installer or manual configuration ?

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
Kiamori

Kiamori

10/25/2011 6:39:03 AM
I did run the sql script without an error, its getting it to work after that point that gives me the error.
This content has not been rated yet. 
61 Reputation 10 Total posts
khorvat

khorvat

10/25/2011 6:38:15 AM
Hi,

you said that you get the error after running the upgrade via MonoX installation, if I understood you well.

After running the createdatabase.sql and going to the url, the platform still takes me to the installer even if I try to remove the /installer directory so I ran the installer again with the option to upgrade after which the error is as follows:

Can you please explain this a bit, as we would like to get the error from the create database script ran against the empty database ?

Basic procedure related to the database is to create an empty database, map an user to it and perform the MonoX installation with first option checked.

You can find more information about MonoX installation here:

IIS and related settings
MonoX installation

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
Kiamori

Kiamori

10/25/2011 1:11:17 PM
Their is no error from the createdatabase.sql script alone, this works fine. After running the createdatabase.sql if I go to the URL it does not think that it is installed yet and therefore takes me back to the installer again. If I attempt to do a regular install at this point it will fail so then I used the installer to do an upgrade which does say successful. However, I still get the error that I previously posted after the upgrade procedure is done.

After running the createdatabase.sql what is the next step?
This content has not been rated yet. 
61 Reputation 10 Total posts
khorvat

khorvat

10/25/2011 2:01:29 PM
Hi,

you should go to the web.config and change the ConnectionString and appSetting called InstallationDone to true.

Let me know if this has solved the issue you have.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
Kiamori

Kiamori

10/25/2011 2:56:34 PM
I ran the createdatabase.sql, updated the web.config file to include the correct connection string and updated the installationdone to true and I get the error that I posted before:

Server Error in '/' Application.
--------------------------------------------------------------------------------The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Page_aspnet_Applications". The conflict occurred in database "monox", table "dbo.aspnet_Applications", column 'ApplicationId'.
The statement has been terminated.
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: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Page_aspnet_Applications". The conflict occurred in database "monox", table "dbo.aspnet_Applications", column 'ApplicationId'.
The statement has been terminated.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 (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Page_aspnet_Applications". The conflict occurred in database "monox", table "dbo.aspnet_Applications", column 'ApplicationId'.
The statement has been terminated.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +109
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +126
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +238
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2313
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +164
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +1034
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +242
System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) +295
System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +117
SD.LLBLGen.Pro.ORMSupportClasses.ActionQuery.Execute() +343[ORMQueryExecutionException: An exception was caught during the execution of an action query: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Page_aspnet_Applications". The conflict occurred in database "monox", table "dbo.aspnet_Applications", column 'ApplicationId'.
The statement has been terminated.. Check InnerException, QueryExecuted and Parameters of this exception to examine the cause of this exception.]
SD.LLBLGen.Pro.ORMSupportClasses.ActionQuery.Execute() +631
SD.LLBLGen.Pro.ORMSupportClasses.BatchActionQuery.Execute() +112
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.ExecuteActionQuery(IActionQuery queryToExecute) +97
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.PersistQueue(List`1 queueToPersist, Boolean insertActions, Int32& totalAmountSaved) +1241
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave, IPredicateExpression updateRestriction, Boolean recurse) +1030
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave) +38
MonoSoftware.LLBLGen.Repository.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave) +51
MonoSoftware.MonoX.Repositories.PageRepository.CreatePage(String url, String template) +396
MonoSoftware.MonoX.Repositories.PageRepository.CreatePage(String url) +28
MonoSoftware.MonoX.Utilities.PageUtility.GetPageProperties(String appRelativeCurrentExecutionFilePath) +197
MonoSoftware.MonoX.BasePage.GetPageProperties() +28
MonoSoftware.MonoX.BasePage.get_PageProperties() +28
MonoSoftware.MonoX.BasePage.OnPreInit(EventArgs e) +54
System.Web.UI.Page.PerformPreInit() +21
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +992
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.237
This content has not been rated yet. 
61 Reputation 10 Total posts
khorvat

khorvat

10/25/2011 3:26:42 PM
Hi,

can you please send us a web.config via direct messages (in the upper right corner) and also can you please check if you have one record in the Aspnet_Applications table. Provide us with the data from that table.

In the meanwhile we will try to reproduce the issue in clean environment.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
Kiamori

Kiamori

10/25/2011 4:44:37 PM
I sent the detached database files as well as the deployed site files via this sites messege system to "denis,khorvat" let me know if you don't get it.
This content has not been rated yet. 
61 Reputation 10 Total posts
khorvat

khorvat

10/26/2011 7:31:04 AM
Hi,

I think that we have managed to reproduce the issue but I'm not 100% sure yet, I'll let you know the outcome soon. Stay tuned.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
khorvat

khorvat

10/26/2011 10:38:31 AM
Hi,

you can find the CreateDatabase.sql and import scripts attached to this post. You need to extract them to the fresh MonoX unzipped package and locations are:

1. /MonoX/Installer/SQL/CreateDatabase.sql
2. /MonoX/Installer/SQL/Import/*.sql

After you do that you can setup the IIS and start the installation process. Let us know if this has fixed the issue you are having ?

Note: We suspect the this is an issue related to SQL script was to big so we have splitted into smaller batches. 

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
1 2 3