Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
When Installing XSLTsearch 3.0.1 from Umbraco Package Repository in a clean Umbraco 4.7.0 installation, the following error appears after clocking "Download and Install package".
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
Exception Details: System.Web.Services.Protocols.SoapException:
System.Web.Services.Protocols.SoapException: Server was unable to
process request. ---> Object reference not set to an instance of an
message, WebResponse response, Stream responseStream, Boolean
asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
packageGuid, String repoVersion) in C:\Users\Hartvig\Documents\Source
Code\Repository Webservices\our\Repository.cs:line 378 at
packageGuid, Version schemaVersion) in C:\Users\Hartvig\Documents\Source
Code\Repository Webservices\Repository.asmx.cs:line 336
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.
[SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Object reference not set to an instance of an object.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
at PackageRepoWebservices.Our.Repository.fetchPackageByVersion(String packageGuid, String repoVersion) in C:\Users\Hartvig\Documents\Source Code\Repository Webservices\our\Repository.cs:line 378
at PackageRepoWebservices.Repository.fetchPackageByVersion(String packageGuid, Version schemaVersion) in C:\Users\Hartvig\Documents\Source Code\Repository Webservices\Repository.asmx.cs:line 336]
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +1485877
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters) +221
umbraco.cms.businesslogic.packager.repositories.RepositoryWebservice.fetchPackageByVersion(String packageGuid, Version schemaVersion) +79
umbraco.cms.businesslogic.packager.repositories.Repository.fetch(String packageGuid, String key) +100
umbraco.presentation.developer.packages.Installer.Page_Load(Object sender, EventArgs e) +650
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
System.Web.UI.Control.OnLoad(EventArgs e) +91
umbraco.BasePages.BasePage.OnLoad(EventArgs e) +14
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
Hmm, shouldn't happen of course. Meanwhile, you can download the package from the project section on our.umbraco.org and install local package from your umbraco installation, that should work.
This looks like an error in the delivery of the package from the repository.
Click the 'Download' link in the top-right of the XSLTsearch page (http://our.umbraco.org/projects/website-utilities/xsltsearch). Do not expand the .zip file, Umbraco will handle it as-is.
Then, in Umbraco, use the 'install local package' item rather than installing from the package repository.
If you get an error installing XSLTsearch because it was partially installed the first time, uninstall it through the Packages section (use the 'Installed packages' item) and then install it again from the local package you downloaded.
Downloading the zip file and installing it as a local package did the trick.
I keep getting this error when I try to install it as either a package or from the repository. I'm running the latest version of umbraco and it will appear under my packages directory. The other dev here started getting this error. I have a theory that the UID is being generated somewhere and it's trying to register this in the db but it's still there from the first time that the package was installed.
Installing a package while the XSLTSearch Package is there is also causing problems.
Has anyone else experienced this problem?
I haven't the slightest idea what this error refers to. When you say, "the latest version of umbraco"... what version are you referring to?
I tell a lie it's version 4.7.1. Basically, this error turns up every time I attempt to install the package. When I look in the web config it's got two entries in there for the last plug-in installed, well technically it has 4 as it ends up appearing twice into the sectiongroup and there are two entries appearing at the bottom of the config that point to the config for the package itself.
I take these out but soon after they will re-appear
Umbraco 4.7.1 is the latest release so that's great.
I'm confused though, XSLTsearch doesn't have any entry in the web.config file at all. Is this a problem with XSLTsearch or some other package? Can you give further details?
I've not touched umbraco for months, it's a great community but I sometimes go months without using it and get confronted with problems at the point where I've forgotten how to use the thing.
Basically what seems to have happened is my boss tried installing the package while I wasn't here and when I got back I found that he'd tried to install it on multiple occasions. I looked and when it was installed I think he got the error above because that's the error I'm getting. When I looked in the installed packages folder I saw that XSLTSearch was appearing multiple times under packages. What I did was to uninstall each instance and try again. This is when I got the above error.
What I then did, once removed was try and install ImageGen which I need for something I was creating. Now from this point onwards what happens is that whenever I try to install another package I get multiple instances of the ImageGen (or presumably any other package) appearing under the web config.
What I am guessing has happened is that the package installed fine but for some reason (maybe db permissions or something) the uniqueID is clashing or not registering during the second part of the install process causing a duplicate ID or something
Once I've installed ImageGen When I go to the admin area of the site while this is there I was noticing that it was informing me that there were multiple duplicates withing the dictionary object used within the content editor.
To resolve this problem I have to go into the web config and remove duplicate entries from the web config that are occuring.
I'd figured that there must be a problem with the package but I guess it's also possible that some other package installed shares the GUID with XSLTSearch. I figured someone else must be getting this error or it must be a common problem.
I should have explained this a bit better. I was working on several things at a time yesterday but hopefully taking my time to explain this properly may prove useful.
Thanks for explaining more.
It sounds like there are probably a couple things going on, each with its own issues that may have a cascade effect. I can only speak to my packages with certainty but since you mentioned them (XSLTsearch and ImageGen) hopefully we can at least get those sorted out. All packages should have a unique GUID but its possible there's a conflict somewhere if a package author didn't make a fresh guid for their package.
With XSLTsearch, if you install it multiple times you will get an error about dictionary keys already installed. In general you can just ignore those and you should be okay (they are already present so no problem in that sense). If you uninstall XSLTsearch it should remove all the dictionary keys and you can install XSLTsearch afresh and shouldn't get the errors.
What you should have when XSLTsearch has been installed is a bunch of dictionary entries (Settings section > Dictionary tree in Umbraco), a search page in the content tree, an XSLTsearch.xslt file in the developer section, an XSLTsearch macro in the developer section, and an xsltsearch.cs file in the site's /app_code folder. If you've got those things you've got XSLTsearch installed properly.
With ImageGen, if you install it more than once you'll get duplicate entries in the web.config file. Even if you uninstall ImageGen you'll still have two entries in the web.config file as the uninstaller can't remove them, so that's a manual step if unisntalling. But if you've got ImageGen installed already you can use the upgrade package to refresh the binary files without going through the full configuration of updating configuration files. It's always safe to use the update package to be sure you don't get double-entries in the web.config or lose any custom settings in your site's /config/imagegen.config file.
With ImageGen installed, you should have three files on the server: imagegen.dll in the site's /bin folder, imagegen.ashx in the root of the site, and imagegen.config in the /config folder. You'll also have two entries at the bottom of the web.config file to reference ImageGen and the imagegen.config file. If those are present then ImageGen is properly installed.
You can verify the installation by visiting localhost/imagegen.ashx?version (replace localhost with your domain) and see the details it returns.
In summary, check the proper items are actually present on the filesystem and within Umbraco. If so then no need to attempt to (un)install again.
Let us know what you find out.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted