IIS6 configuration
Hello,
Have followed instructions to install on windows server 2003 with IIS6. All per-requisites are installed.
When following the instruction to browse to new created virtual directory, I get a 403 error, most likely due to no default document, and directory browsing is disable.
I cannot seem to find the answer for the question, how do you configure IIS6 to point to the proper initial start page? Is it a .dll, .cgi file, or something else?
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by longislanddan on 13 Nov, 2013 07:49 PM
I have found the configuration that handles this. So, in the web.config you are redirecting to a class. It appears there are missing installation instructions for adding handlers to handle the type of class that the web.config is redirecting to.
Can you provide a suggestion for the missing handlers in IIS that will resolve this problem?
2 Posted by longislanddan on 13 Nov, 2013 09:53 PM
Slowly working my way through the issues.
Had to allow wildcard access through the .net isapi dll. This resolved some issues.
The I found in event log that the IIS Admin needed additional rights through COM server configuration.
Now The site "starts" to render, but am getting the following error in the log:
[ SELECT this_.ID as ID5_0_, this_.Name as Name5_0_, this_.Description as Descript3_5_0_, this_.Status as Status5_0_, this_.SecurityMode as Security5_5_0_, this_.MainlineBranch as Mainline6_5_0_, this_.ProjectID as ProjectID5_0_, this_.StatsCommits as StatsCom8_5_0_, this_.StatsLastCommitAt as StatsLas9_5_0_, this_.StatsCommitActivity as StatsCo10_5_0_, this_.StatsSize as StatsSize5_0_, this_.StatsTipChangesetNodeID as StatsTi12_5_0_, this_.StatsRefreshedAt as StatsRe13_5_0_ FROM [Repository] this_ ]
[SQL: SELECT this_.ID as ID5_0_, this_.Name as Name5_0_, this_.Description as Descript3_5_0_, this_.Status as Status5_0_, this_.SecurityMode as Security5_5_0_, this_.MainlineBranch as Mainline6_5_0_, this_.ProjectID as ProjectID5_0_, this_.StatsCommits as StatsCom8_5_0_, this_.StatsLastCommitAt as StatsLas9_5_0_, this_.StatsCommitActivity as StatsCo10_5_0_, this_.StatsSize as StatsSize5_0_, this_.StatsTipChangesetNodeID as StatsTi12_5_0_, this_.StatsRefreshedAt as StatsRe13_5_0_ FROM [Repository] this_] ---> System.Data.SqlClient.SqlException: Invalid object name 'Repository'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
Any ideas?
Support Staff 3 Posted by Anton Gogolev on 14 Nov, 2013 05:23 AM
Dan,
Is there a chance for us to set up a TeamViewer session so that I could see where the problem is? I'd really love to nail down the installation aspect so that it would be as simple as possible and I'd like to see what's wrong with your particular case.
4 Posted by longislanddan on 14 Nov, 2013 01:54 PM
I have a better idea...
As a developer who can literally find a problem with anything software and hardware related, I would be more than willing to remote debug my local server installation using source code, if you are willing.
I am well versed in the .Net framework languages, along with java, the scripting versions of java, python, ruby, etc. I think I would be able to resolve the issue locally much faster. Having a remote session unfortunately is not an option due to corporate policy.
We could go over handling of source code, rules, etc via private conversation.
You have my email from my postings, drop me an email and let me know.
5 Posted by longislanddan on 14 Nov, 2013 02:14 PM
Getting further...
Looking at the log files entry from above, it cannot see the Environment table.
Looking at the database, there are NO tables. It appears the database creation script is not running.
16:50:44.4080 - Info - - octalforty.Structural.Framework.Web.MvcApplication - starting application
16:50:44.4393 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initializing service provider factory
16:50:44.4393 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initialized service provider factory
16:50:44.4393 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initializing middleware pipeline
16:50:44.4549 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initialized middleware pipeline
16:50:44.4549 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initializing service provider
16:50:44.4549 - Info - - octalforty.Structural.ComponentModel.ServiceProviderFactory - started building container
16:50:47.1112 - Info - - HgLab.Core.Configuration.Modules.PersistenceModule - building session factory
16:50:47.8300 - Info - - HgLab.Core.Configuration.Modules.PersistenceModule - built session factory
16:50:47.9863 - Info - - octalforty.Structural.ComponentModel.ServiceProviderFactory - finished building container
16:50:47.9863 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initialized service provider
16:50:47.9863 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initializing framework
16:50:48.0175 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initialized framework
16:50:48.0175 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initializing services
16:50:48.0956 - Info - - octalforty.Structural.ComponentModel.Jobs.JobRuntimeService - starting thread for job 'HgLab.Core.Jobs.RepostoryStatsRefreshJob'
16:50:48.1113 - Info - - octalforty.Structural.ComponentModel.Jobs.JobRuntimeService - started thread for job 'HgLab.Core.Jobs.RepostoryStatsRefreshJob'
16:50:48.1113 - Info - - octalforty.Structural.ComponentModel.Jobs.JobRuntimeService - starting thread for job 'HgLab.Core.Jobs.DeploymentTrackerJob'
16:50:48.1113 - Info - - octalforty.Structural.ComponentModel.Jobs.JobRuntimeService - started executing thread for job 'HgLab.Core.Jobs.RepostoryStatsRefreshJob'
16:50:48.1113 - Info - - octalforty.Structural.ComponentModel.Jobs.JobRuntimeService - started thread for job 'HgLab.Core.Jobs.DeploymentTrackerJob'
16:50:48.1113 - Info - - octalforty.Structural.ComponentModel.Jobs.JobRuntimeService - started executing thread for job 'HgLab.Core.Jobs.DeploymentTrackerJob'
16:50:48.1113 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initialized services
16:50:48.1113 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initializing routes
16:50:48.1581 - Info - - octalforty.Structural.Framework.Web.MvcApplication - initialized routes
16:50:48.1581 - Info - - octalforty.Structural.Framework.Web.MvcApplication - started application
16:50:48.3769 - Error - - octalforty.Structural.ComponentModel.Jobs.JobRuntimeService - could not execute JobThreadProc for job 'HgLab.Core.Jobs.RepostoryStatsRefreshJob'. increasing failsafe interval to 00:00:20NHibernate.Exceptions.GenericADOException: could not execute query
[ SELECT this_.ID as ID5_0_, this_.Name as Name5_0_, this_.Description as Descript3_5_0_, this_.Status as Status5_0_, this_.SecurityMode as Security5_5_0_, this_.MainlineBranch as Mainline6_5_0_, this_.ProjectID as ProjectID5_0_, this_.StatsCommits as StatsCom8_5_0_, this_.StatsLastCommitAt as StatsLas9_5_0_, this_.StatsCommitActivity as StatsCo10_5_0_, this_.StatsSize as StatsSize5_0_, this_.StatsTipChangesetNodeID as StatsTi12_5_0_, this_.StatsRefreshedAt as StatsRe13_5_0_ FROM [Repository] this_ ]
[SQL: SELECT this_.ID as ID5_0_, this_.Name as Name5_0_, this_.Description as Descript3_5_0_, this_.Status as Status5_0_, this_.SecurityMode as Security5_5_0_, this_.MainlineBranch as Mainline6_5_0_, this_.ProjectID as ProjectID5_0_, this_.StatsCommits as StatsCom8_5_0_, this_.StatsLastCommitAt as StatsLas9_5_0_, this_.StatsCommitActivity as StatsCo10_5_0_, this_.StatsSize as StatsSize5_0_, this_.StatsTipChangesetNodeID as StatsTi12_5_0_, this_.StatsRefreshedAt as StatsRe13_5_0_ FROM [Repository] this_] ---> System.Data.SqlClient.SqlException: Invalid object name 'Repository'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
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.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
at NHibernate.AdoNet.AbstractBatcher.ExecuteReader(IDbCommand cmd) in d:\CSharp\NH\NH\nhibernate\src\NHibernate\AdoNet\AbstractBatcher.cs:line 252
Support Staff 6 Posted by Anton Gogolev on 15 Nov, 2013 11:06 AM
Sorry for the delayed responses: apparently, we are very far apart timezone-wise.
Looks like you're almost there. The problem you're experiencing has nothing to do with code. It's purely a configuration issue.
Running ASP.NET 4.0 applications under IIS 6.0 require a bit of tinkering. See this and this. However, judging by the fact that you see database-related exceptions you were able to start HgLab.
These errors that you are seeing are side-effects of a pre-release version and will not be there in release. They are caused by background jobs that do all kinds of stuff, occasionally hitting the database, which has not been set up yet.
HgLab creates (and updates) databases only after you explicitly tell it to via the web interface. All there's left to do for you is to somehow make the web page appear inside a browser.