Initial Installation Setup Error: XML Parsing Error: no element found

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.
8/13/2007 12:57:07 PM
Gravatar
Total Posts 9

Initial Installation Setup Error: XML Parsing Error: no element found

Hello,

I get the following error when I go to the site:

XML Parsing Error: no element found
Location: http://www.ksayre.com/Setup/Default.aspx
Line Number 1, Column 1:
^

I'm not sure what I may have missed.  I have setup the web.config with the connection, and the settings for a medium trust site.  Any insites?  I'm running on IIS with SQL Server 2005.

Thanks.

~Kevin

8/13/2007 5:11:02 PM
Gravatar
Total Posts 18439

Re: Initial Installation Setup Error: XML Parsing Error: no element found

Can you try the new 2.2.3.4 files? Setup has a lot of improvements and may help past this problem.

Joe

8/14/2007 9:40:09 AM
Gravatar
Total Posts 9

Re: Initial Installation Setup Error: XML Parsing Error: no element found

Ok, I've installed the newest version, and get further than before, but now this error appears:

Running script mojoportal-core - 2.2.3.4 - 00:00:01.0937430
An Error Occurred:Failed to convert parameter value from a Guid to a String.
Source:System.Data
Stack Trace at System.Data.SqlClient.SqlParameter.CoerceValue(Object value, MetaType destinationType) at System.Data.SqlClient.SqlParameter.GetCoercedValue() at System.Data.SqlClient.SqlParameter.Validate(Int32 index) at System.Data.SqlClient.SqlCommand.SetUpRPCParameters(_SqlRPC rpc, Int32 startCount, Boolean inSchema, SqlParameterCollection parameters) at System.Data.SqlClient.SqlCommand.BuildRPC(Boolean inSchema, SqlParameterCollection parameters, _SqlRPC& rpc) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at mojoPortal.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at mojoPortal.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at mojoPortal.Data.dbPortal.SchemaVersion_GetSchemaVersion(Guid applicationID) at mojoPortal.Data.dbPortal.SchemaVersion_Exists(Guid applicationID) at mojoPortal.Business.DatabaseHelper.UpdateSchemaVersion(Guid applicationID, String applicationName, Int32 major, Int32 minor, Int32 build, Int32 revision) at mojoPortal.Web.UI.Pages.SetupHome.RunScripts(Guid applicationID, String applicationName, String pathToScriptFolder) at mojoPortal.Web.UI.Pages.SetupHome.CreateInitialSchema(String applicationName) at mojoPortal.Web.UI.Pages.SetupHome.RunSetup() at mojoPortal.Web.UI.Pages.SetupHome.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

8/14/2007 10:03:49 AM
Gravatar
Total Posts 18439

Re: Initial Installation Setup Error: XML Parsing Error: no element found

I sent you a new mojoPortal.Business.dll to try and see if it fixes the problem. You probably will need to clean out the db.

Can you tell me anything about your runtime environment and what culture it is localized to?

Thanks,

Joe

8/14/2007 10:06:58 AM
Gravatar
Total Posts 18439

Re: Initial Installation Setup Error: XML Parsing Error: no element found

I just looked at your site and saw the setup page. This is an upgrade right? Not a clean install? If it were a clean install it would start with script 2.2.3.4.

Can you look in mp_SchemaVersion, if the application name is not lower case like this: mojoportal-core, can you change it to be lower case?

Joe

8/14/2007 10:09:23 AM
Gravatar
Total Posts 18439

Re: Initial Installation Setup Error: XML Parsing Error: no element found

Actually since no site have been created, you would probably have best results if you delete all db objects, ie. stored procedures and tables and let it do a clean creation of the db objects. It should start with script 2.2.3.4 and then it should not need to run any upgrade scripts.

Joe

8/14/2007 10:42:07 AM
Gravatar
Total Posts 9

Re: Initial Installation Setup Error: XML Parsing Error: no element found

Yeah, it's a new install.  I cleared out and ran again with the same result using the new dll you sent me.  It must get through some of the script because it thinks it's an upgrade the second time around.

I'm hosting at 1and1.com, so this is the best I know of the runtime environment.  ASP.NET 2.0, medium trust, and I believe en-US using IIS on Windows 2003.  It's also a shared environment.

Hopefully that helps more.

Thanks for your help and quick responses.

~Kevin

 

 

8/14/2007 10:53:18 AM
Gravatar
Total Posts 9

Re: Initial Installation Setup Error: XML Parsing Error: no element found

Another interesting note, it seems to create the tables and procedures, but none of the tables have any rows.

8/14/2007 11:04:10 AM
Gravatar
Total Posts 18439

Re: Initial Installation Setup Error: XML Parsing Error: no element found

I don't think you got everything cleared out otherwise it would not be trying to run script 2.2.1.5 and it would not say database initial schema already exists when it probes the system.

Are you sure you uploaded all the files for the new version?

Rows will be added after the schema is upgraded.

Try deleting everything again, if you get the same result again then delete everything once more and try running the script manually from query analyzer or whatever db tool your host provides. The script is located at webroot/Setup/applications/mojoportal-core/SchemaInstallScripts/2.2.3.4.config

Hope it helps,

Joe

8/14/2007 11:28:48 AM
Gravatar
Total Posts 18439

Re: Initial Installation Setup Error: XML Parsing Error: no element found

I forgot to say if you do run the script manually you will need to insert a row in mp_SchemaVersion with application name mojoportal-core, application id = 077e4857-f583-488e-836e-34a4b04be855, and 2 2 3 4 for major minor build revision

Joe

8/14/2007 12:13:08 PM
Gravatar
Total Posts 9

Re: Initial Installation Setup Error: XML Parsing Error: no element found

Ok, I'm going to go ahead and run the script manually.

It ran the most recent script, note the version number in the post that has the parse error.

It's just when it is hit/refreshed after that initial one that it displays the upgrade message.

I'll keep you posted on the results of the newest attempt.

Thanks.

~Kevin

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