Hmm weird thing is, the code inside the InstallTable method is surrounded by Try/Catch which should give user-friendly error messages when someting goes wrong. Is it possible for you to detect the output of the AJAX POST to that URL by using Firebug/Fiddler?
BTW, what DB are you using? MS SQL? Which version?
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.ArgumentNullException: Value cannot be null. Parameter name: stream
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.
I've tried reproducing with IIS Express, but it's working fine for me. The custom VirtualPathProvider I'm talking about is also responsible for showing the installer usercontrol, which looks to be working fine. The stack trace also doesn't show any of my code...
I think your buildProviders are different than mine. In the web.config there's this element called <buildProviders>. Could you add the following to it:
The provided stream is null, which is one of the 'referencedAssemblies'. So please check the assemblies you are referencing, there might be something weird going on there. You might also want to try to install the Url Tracker in a clean umbraco v4.8 installation, I think it's someting project-specific...
Thanks for testing :-) The Http Module error is fixed in the latest version (2.0.2-beta). I didn't take ports other than 80 into account. SqlCE support is planned (see Roadmap on the project's page).
Stuck at Installing the Database table (Umbraco 4.8)
Hey Stefan,
Congratulations on the relase, cheers for the great package.
Getting an install error, db permissions seem fine but had the 'Installing the Database table' screen for > 5 minutes
Tested previous version (1.5.2) and it installed fine, any ideas?
Thanks
Rich
Hmm weird thing is, the code inside the InstallTable method is surrounded by Try/Catch which should give user-friendly error messages when someting goes wrong.
Is it possible for you to detect the output of the AJAX POST to that URL by using Firebug/Fiddler?
BTW, what DB are you using? MS SQL? Which version?
I've installed the older version for now, will try as soon as I can to replicate and check the Ajax post.
Okay, and how about the SQL edition/version?
Hey,
Sorry for the delay, problem is probably because I'm using SQL Server 2012 (11.0.2100.60)
Here's the output, if you wanted something different let me know as I can reproduce it.
Cheers
Rich
http://localhost:49173/Umbraco/UrlTracker/InfoCaster.Umbraco.UrlTracker.UI.Installer.UrlTrackerInstallerService.asmx/installtable
Server Error in '/' Application.
Value cannot be null.
Parameter name: stream
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.ArgumentNullException: Value cannot be null.
Parameter name: stream
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:
[ArgumentNullException: Value cannot be null.
Parameter name: stream]
System.IO.StreamReader..ctor(Stream stream, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean leaveOpen) +10590213
System.IO.StreamReader..ctor(Stream stream, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize) +20
System.Web.UI.SimpleWebHandlerParser.Parse(ICollection referencedAssemblies) +113
System.Web.Compilation.SimpleHandlerBuildProvider.get_CodeCompilerType() +68
System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) +140
System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() +205
System.Web.Compilation.BuildProvidersCompiler.PerformBuild() +16
System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) +498
System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +364
System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +103
System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) +128
System.Web.Compilation.BuildManager.GetCompiledType(VirtualPath virtualPath) +10
System.Web.Compilation.BuildManager.GetCompiledType(String virtualPath) +25
System.Web.Script.Services.WebServiceData.GetWebServiceData(HttpContext context, String virtualPath, Boolean failIfNoData, Boolean pageMethods, Boolean inlineScript) +211
System.Web.Script.Services.RestHandler.CreateHandler(HttpContext context) +126
System.Web.Script.Services.RestHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String pathTranslated) +59
System.Web.Script.Services.ScriptHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String pathTranslated) +48
System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +434
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +157
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18045
It's my custom VirtualPathProvider, which is responsible for the AJAX call's URL being available.
I've only tested this with IIS. Which are you using; IIS Express or the WebDev server Cassini?
Thanks in advance!
Ahh, IIS Express as it's local dev site
Rich
I've tried reproducing with IIS Express, but it's working fine for me.
The custom VirtualPathProvider I'm talking about is also responsible for showing the installer usercontrol, which looks to be working fine.
The stack trace also doesn't show any of my code...
I think your buildProviders are different than mine.
In the web.config there's this element called <buildProviders>. Could you add the following to it:
Hmm I think it's something else. If I look at the stack trace, one of the upper lines is:
And followed by:
The provided stream is null, which is one of the 'referencedAssemblies'.
So please check the assemblies you are referencing, there might be something weird going on there.
You might also want to try to install the Url Tracker in a clean umbraco v4.8 installation, I think it's someting project-specific...
Hey,
Cheers for taking a look, I imagine it's project specific, it's something we inherited and are rebuilding as it's all over the place.
We'll use the existing version for now!
Thanks again
Rich
(I tried adding those lines to web.config but no joy)
Can you also try to install in a clean umbraco v4.8?
To verify that it really is a project-specific issue?
Sure thing! Will let you know
Clean install of 4.8, using SQL Server (as above) table creation worked fine, only note was:
Checking the Http Module.
The Http Module isn't installed: The Http Module isn't responding.
On a side note, originally tried to install it using SQLCE (clean install of 4.8) and got the error below.
Not sure if SQLCE was supposed to be supported.
Hope it helps!
Again, cheers for the great package.
Rich
Hey Rich,
Thanks for testing :-)
The Http Module error is fixed in the latest version (2.0.2-beta). I didn't take ports other than 80 into account.
SqlCE support is planned (see Roadmap on the project's page).
Could you mark this topic as resolved if you agree?
SqlCE is now supported. Could you close this topic Rich?
Yep! Many thanks :)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.