Server Error in '/Iceberg' Application. There is no ProcessRuntime available, or ProcessRuntime.Current was not set. Can not retrieve Connection String. 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.NullReferenceException: There is no ProcessRuntime available, or ProcessRuntime.Current was not set. Can not retrieve Connection String.
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:
[NullReferenceException: There is no ProcessRuntime available, or ProcessRuntime.Current was not set. Can not retrieve Connection String.] Fractis.ProcessFlow.Utility.DataUtil.PrepareConnection(SqlCommand command) +150 Fractis.ProcessFlow.Utility.DataUtil.PrepareCommandAndConnection(SqlCommand command, Object[] parameters) +43 Fractis.ProcessFlow.Utility.DataUtil.ExecuteScalarInternal(SqlCommand command, Object[] parameters, Boolean literalSql) +46 Fractis.ProcessFlow.Utility.DataUtil.SpExecuteScalar(String sprocName, Object[] paramaters) +51 Iceberg.Web.Core.IcebergUser.get_IsAdmin() +86 Iceberg.Web.UI.Pages.PageBase.OnInit(EventArgs evt) +56 System.Web.UI.Control.InitRecursive(Control namingContainer) +321 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +834 Version Information: Microsoft .NET Framework Version:2.0.50727.1434; ASP.NET Version:2.0.50727.1434
As far as I can tell I have everything set up properly... I'm not 100% on the connection string (I normally use a different format) <add name="Iceberg.Data.Properties.Settings.IcebergConnectionString" connectionString="Data Source=.\SQLEXPRESS; Initial Catalog=Iceberg; Persist Security Info=True; User ID=IcebergUser; Password=i1c2e3; Connection Timeout=90" providerName="System.Data.SqlClient" />
I'm pretty stuck with trying to get it working. ... This is an internal/code/unknown web.config/ect problem... In short - I don't know where to even try to look to attempt to fix the issue with custom Exceptions like this one.
Any pointers would be great. :) I'm using the ZIP file and installing everything, the installer mega failed, and I'm better at fixing things when I can play with them like with what the zip provides... this just is too specific to iceberg for me to know what to try.
I think this could do something awesome for me and a project I'm developing... just gotta get it working first.
And... I solved my own problem... Sometimes it takes that little bit to remember - In IIS 7 you need to put the Application Pool to "Classic .NET AppPool" I had to do this for DotNetNuke before, only reason I knew.
Thats right, IIS7 compatibility is still not 'officially' supported, but 99% of the time it works in ISAPI/classic mode. The actual cause of that error is that the process runtime HttpModule is not being registered correctly, as the config file format differs in IIS7 integrated mode, and hence it never loads and initializes the runtime. Integrated mode support is on the way very soon.
Yea we figured people handy with IIS would prefer to just get their hands on the files in a zip and set them up manually.
Just out of curiosity, what made the automated installation blow up?
All the best with the project, I hope Iceberg helps you out, don't be afraid to let us know how you get on :)
I think the issue was addressed in another thread, but I was getting "Page Cannot be Displayed" from IE and "Firefox has detected that the server is redirecting the request for this address in a way that will never complete." when I tried to use the exe version. Firefox redirected from http://localhost:31833/ to http://localhost:31833/UI/Pages/InvalidConfiguration.htm?/ before giving me the error.
I turned off the custom errors and got "Generating user instances in SQL Server is disabled. Use sp_configure 'user instances enabled' to generate user instances." I think I'd have to do about the same level of work to get the installer version to work as the zip file... Since it doesn't seem to have SQL set up, ect. By mega failed - It was more "I encountered no errors during set up, got the start page saying everything was set up, and then it wouldn't load. The Cassini server says it's running "EDIT/REGISTER Iceberg Running 31833 C:\Program Files\Fractis\Iceberg\Web " but navigating to it yielded only errors.
For me, and it may be a bad thing - If it has an installer, I expect it to work once the installer is finished. No tweaking files or any of that, installed = working. With just the zip files, I accept/know there is going to be tweaking and working to get it set up so it runs. It's the lazy and techie side of me.
No you're definitely right, the express install is meant to be a no brainer. The dependency on SQL Server Express is the thing that causes most of the headaches. We're working through the issues as they come up to try make sure they don't happen to the next guy, so the feedback is appreciated
The problem you mention (user instances not allowed) is indeed easily fixable: