Gold installation problem

[HaggisMan]

I'm bringing a 7.0.4 site up to Gold ( 7.0.8 ). The upgrade to 7.0.7 went fine. I then installed a new site for Gold, following the Gold Upgrade instructions with the intent of upgrading the DB and migrating custom stuff into the Gold site:

*stopped the 7.0.7 site after verifying the database was upgraded
*installed .NET4
*Created an empty folder for the site, set permissions appropriately.
*Created a .NET 4 application pool.
*Copied the Gold files from Ablecommerce-GOLDR-b5410-WSP.zip file to the folder.
*Created a site in IIS, pointed it to the folder. Started App pool and site.
*Following the Gold Upgrade instructions, I attempted to access http://mysiteurl/install/default.aspx. Instead of the expected "enter license key" and "where's the database" screens I get the following error:

Code: Select all

Server Error in '/' Application.
--------------------------------------------------------------------------------

Format of the initialization string does not conform to specification starting at index 0. 
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.ArgumentException: Format of the initialization string does not conform to specification starting at index 0.

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: 


[ArgumentException: Format of the initialization string does not conform to specification starting at index 0.]
   System.Data.Common.DbConnectionOptions.GetKeyValuePair(String connectionString, Int32 currentPosition, StringBuilder buffer, Boolean useOdbcRules, String& keyname, String& keyvalue) +6298813
   System.Data.Common.DbConnectionOptions.ParseInternal(Hashtable parsetable, String connectionString, Boolean buildChain, Hashtable synonyms, Boolean firstKey) +253
   System.Data.Common.DbConnectionOptions..ctor(String connectionString, Hashtable synonyms, Boolean useOdbcRules) +134
   System.Data.SqlClient.SqlConnectionString..ctor(String connectionString) +103
   System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous) +35
   System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(String connectionString, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions) +253
   System.Data.SqlClient.SqlConnection.ConnectionString_Set(String value) +60
   NHibernate.Connection.DriverConnectionProvider.GetConnection() +221
   NHibernate.Tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.Prepare() +28
   NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.GetReservedWords(Dialect dialect, IConnectionHelper connectionHelper) +113
   NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.Update(ISessionFactory sessionFactory) +125
   NHibernate.Impl.SessionFactoryImpl..ctor(Configuration cfg, IMapping mapping, Settings settings, EventListeners listeners) +865
   NHibernate.Cfg.Configuration.BuildSessionFactory() +154
   CommerceBuilder.Common.DatabaseConfiguration.get_SessionFactory() +584
   CommerceBuilder.Common.DatabaseSessionManager.GetSession() +355
   CommerceBuilder.DomainModel.NHibernateHelper.CreateCriteria(String aliasName, Int32 maximumRows, Int32 startRowIndex, String sortExpression) +67
   CommerceBuilder.DomainModel.NHibernateHelper.CreateCriteria(Int32 maximumRows, Int32 startRowIndex, String sortExpression) +92
   CommerceBuilder.DomainModel.RepositoryWithTypedId`2.LoadAll(String sortExpression, Int32 maximumRows, Int32 startRowIndex) +128
   CommerceBuilder.Common.AbleContext.a() +224
   CommerceBuilder.Common.AbleContext.get_Store() +72
   CommerceBuilder.UI.AbleCommercePage.InitializeTheme() +45
   System.Web.UI.Page.PerformPreInit() +49
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1700

 --------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1 

According to IIS and aspnet_regiis, .NET 4 is installed and allowed. I created a simple html file and put it in the root of the website. I get the same error when I try to access the html file.

The server is running:
Windows Server 2008 Standard (Version 6.0 Build 6002: Service Pack 2) 64bit
IIS 7.0.6000.16386
There are other websites, all running .NET2/3.51. All other sites are stopped.
IIS 6.0 is installed for simple SMTP service


I did a similar upgrade of a 7.0.7 site on a Windows 2008R2/IIS7.5 with no problems - http://thatotherurl/install/default.aspx ran just fine.

Any thoughts or hints?

Thanks!

HaggisMan

[ForumsAdmin]

I suggest that you recheck your connection string. I assume you are using SQLServer 2008
http://www.connectionstrings.com/sql-server-2008

[HaggisMan]

The connection string isn't set up yet. The error occurs when I try running the /install/default.aspx script to actually do the install. The script doesn't run - instead of asking me for the Gold license key and then gathering the information to set up the connection string, it throws the error described. This is still the installation process, which isn't complete until /install/default.aspx runs and sets up the license and database configs.

Regards,

HaggisMan

[AbleMods]

Did you physically bounce the whole server after installing .Net 4.0?

Usually installing .Net 4.0 requires a full server reboot to finalize. Restarting IIS or the WWW service isn't enough is most cases.

[ForumsAdmin]

For some reason when you are going to /install/default.aspx you are getting redirected to /default.aspx
Something is not right with your configuration. Make sure website/application is configured right.
Are you setting up the application on a main domain or a sub-folder? It should work in both cases if setup right. Are you by any chance installation it as a sub-application of another application?

[HaggisMan]

Yes, the server was rebooted after .Net4 was installed. The website is in a folder at the drive's root and answers to abc.xyz.com. The site isn't defined as an application, should it be? I haven't tried destroying the website and app pool yet, but that may be the next step. As I mentioned in the original post, I did the same thing a few weeks ago on a different server (W2008R2, IIS7.5) with no problems.

Thanks,

HaggisMan

[ForumsAdmin]

Configuration issues are usually hard to detect easily. At times one could miss something too obvious and at times it could be something deeply convulted configuraion related issue in very specific setup.

I sugges that you do step by step debugging.
First try to see if you can access a simple html file placed in the root of your abc.xyz.com. http://abc.xyz.com/test.html
Then try to see if you can access a simple html file placed in the /install folder
Next you can try to see if you can access a simple aspx file in the root folder. Something like abc.xyz.com/test.aspx
Then you can try to see if you can access simple aspx file inside the /install folder
I think that by this time you will be able to figure out the actual problem because it appears that you are getting redirected to site home when accessing /install

[HaggisMan]

I tried the simple html file route; it generates the same error. I may just uninstall and reinstall .NET4 and see what happens.

[AbleMods]

If a 1-page HTML site throws that error, asp.net isn't your problem. Asp.net isn't used on pure HTML sites.

Uninstall and reinstall IIS.

[HaggisMan]

True, .Net 4 wasn't the problem, but uninstall/reinstall ruled that out completely. The problem was two-fold:

I had created a new website for the Gold installation/Upgrade. The new site was missing two important Authentication elements: In IIS Manager under IIS/Authentication, only Anonymous authentication was enabled. I enabled Forms Authentication but still received the same error. IIS/Authorization Rules contained no rules at all. Adding an Allow rule for All Users pulled the final nail from the metaphorical coffin - html file loaded, /install/default.aspx ran like a charm. I believe that IIS Manager has an Allow rule for All Users at the server level by default, so new sites should inherit that. In this case, I'm guessing that a security-minded person removed it. Moral - check authentication and authorization settings in IIS Manager, just in case.

Thanks again for your help on this.

HaggisMan

[AbleMods]

Glad you got it resolved.

Makes you wonder what other surprises await your discovery