I just installed the Multi Tenancy Module on my Orchard, I may have misconfiguration a new tenant by pointing the new tenant to use the host: localhost in the modules config for testing, and now I get a nasty error disabling the entire application.
Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.
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.ObjectDisposedException: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.
I'm new to Orchard having just set up a 2008 server on the free tier on AWS today. I would like to know the simplest way to recover. Should I backup the Orchard Directory and the Database prior to fiddling in future?
You can edit the settings files for each tenant. They are under app_data/sites/TENANT.
Related
I am finding we receive this error:
Failed to invoke 'CreateChatRequest' due to an error on the server. HubException: Method does not exist.
at _this.callbacks.<computed> (chat.min.js:2060)
at HubConnection.processIncomingData (chat.min.js:2154)
at WebSocketTransport.HubConnection.connection.onreceive (chat.min.js:1881)
at WebSocket.webSocket.onmessage (chat.min.js:3922)
The method does exist. The code does work, then after a while of testing, it returns this and won't stop.
What seems to temporarily fix the issue is restarting the Azure SigR service, but it comes back. This issue does not occur when targeting local SigR during development; it only happens against Azure SigR.
According to documentation, this seems to be a catchall error when something errors up on the server but, no exceptions are being logged. I've turned on detailed errors, but that didn't change the error coming back from the server. I've also tried catching the exception and sending back a HubException to see what is going on, but that didn't change the error message either.
TIA for any help.
So the answer, for me, was that i'd checked in (to source control) my azure service's connection string, so other devs were also using this and pointing their versions of the API service at that azure service. So when i ran my code sometimes azure would hit my API service with the new method in and it would work, sometimes it would hit someone else's API service and so fail because their code didn't have the new method in.
Problem:
We applied some windows updates to our SharePoint server 2013 WFE. This update caused our search service application to break. It is giving following error from search service application in CA:
The search application 'Search Service Application' on server C....1 did not finish loading. View the event logs on the affected server for more information.
To investigate the root cause of the problem I check Event log and found following error :
The Execute method of job definition Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition (ID a006ef86-4d33-4f2d-a77f-4cb2ac909b23) threw an exception. More information is included below.
The search application '102a182f-24fd-4147-8bc4-d22168b3e29e' on server CBRDEVSPS01 did not finish loading. View the event logs on the affected server for more information.
I also checked ULS log and find following error:
11/17/2015 10:23:57.06 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Search Administration dl1x High Unexpected exception caught in GathererProject::EnsureComServer. Exception message: The device is not ready. . 4f4e429d-c15d-5048-e5da-799794211bff
11/17/2015 10:23:57.06 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Search Administration fwi9 Exception search application Search Service Application: synchronization of default content sources failed System.IO.FileNotFoundException: The device is not ready. at Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherApplication2.get_GatherProjects() at Microsoft.Office.Server.Search.Administration.GathererProject.get_ProjectObject() at Microsoft.Office.Server.Search.Administration.GathererProject.EnsureComServer() at Microsoft.Office.Server.Search.Administration.GathererProject.GetContentSource(String strContentSource) at Microsoft.Office.Server.Search.Administration.OSSPrimaryGathererProject.ProvisionContentSources() at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.SynchronizeDefaultContentSources() at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Synchronize() StackTrace: at Microsoft.Office.Server.Native.dll: (sig=678c0f87-966f-4d99-9c94-b49e788d2672|2|microsoft.office.server.native.pdb, offset=131CE) at Microsoft.Office.Server.Native.dll: (offset=21BE5) 4f4e429d-c15d-5048-e5da-799794211bff
11/17/2015 10:23:57.07 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Search Administration fwj8 Exception failed to synchronize application Search Service Application System.IO.FileNotFoundException: The device is not ready. at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Synchronize() at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() StackTrace: at Microsoft.Office.Server.Native.dll: (sig=678c0f87-966f-4d99-9c94-b49e788d2672|2|microsoft.office.server.native.pdb, offset=131CE) at Microsoft.Office.Server.Native.dll: (offset=21BE5) 4f4e429d-c15d-5048-e5da-799794211bff
11/17/2015 10:23:57.12 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Shared Services 6482 Critical Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (64d2ce6d-5c68-4c52-93b8-d0abdaf1dd18). Reason: The device is not ready. Technical Support Details: System.IO.FileNotFoundException: The device is not ready. at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob) 4f4e429d-c15d-5048-e5da-799794211bff
To Solve it I tried following:
Restart the SharePoint Server Search through PowerShell but could not complete the action.
Clear file system Cashed on all WFE where SharePoint Timer Service is running http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance
Uninstall all the Windows Update
Tried to reset search index and stop crawling using PowerShell command and failed to do.
Run the SharePoint product configuration wizard
Check the group policy log and find nothing Impacted SharePoint Accounts.
I created a new search Application which is fully functional. Any Advise to fix the current search Application will be highly appreciated.
I think you're right that there are times when the only solution is to recreate the SSA. I'm in a similar situation right now after installing Windows Updates. The current search index is returning results, but new crawls will not complete and just seem to hang. It can take days to crawl all the content on this farm, so to minimize downtime, here is the plan we are about to implement:
Create a temporary web application.
Create a new Search Service Application associated with the new web
app.
Create content sources in the new SSA
Export managed properties from the old SSA using a PowerShell script like the one described here (http://blog.riccardocelesti.it/exportimport-managed-properties-via-powershell/)
Crawl the content with the new SSA
Import managed properties and mappings (again using the script above)
Switch the service app associations so the production web app uses
this new SSA. It should contain all the crawled content and be ready to respond to queries with current data.
I hope this helps someone.
Only option was to re-create search Servcie Application. Can I avoid creating SSA. Any idea guys?
one of the windows update probably installed a part of one of the earlier CUs. see https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/
Have you tried running the product config wizard (or psconfig)? This might fix you search problems.
Classic ASP application on a locally hosted server (IIS7). Everyone else in the organization can access this application just fine. This specific user encounters the following error:
Active Server Pages error 'ASP 0115'
Unexpected error
/OurApp/OurApp.asp
A trappable error (C0000005) occurred in an external object. The script cannot continue running.
I've found this article on MSDN. However, since all users bar one are able to access this application, the problem doesn't seem to be a general permissions problem.
What might be causing this specific user to run into errors?
0xC0000005 is the access violation error, its not about permission, is about attempting to read or write protected memory. There must be a user based logic in the OurApp.asp script or one or more components in it which attempts to read or write protected memory just in case of this specific user.
I'm trying to figure out why I'm getting 500 errors in setting up a website in IIS.
So far I've tried the following steps:
Enabled Failed Request Tracing (Doesn't write logs for this site, but
works for other sites)
Enabled detailed error messages. Still Getting the default 500 page
with no additional information.
Give app pool full permission to the project directory.
Made sure app pool was running on classic .NET 2 (old app)
Running the site under a permutation of (Classic/Integrated, .NET
2/4)
Enabled anonymous authentication
So my thinking is, somehow, the site fails before the logging modules are ran.
I suspect this is the case because I see no new entities in Event Viewer, IIS Advanced Logs folder, Or in Failed Request Tracing folder. My only source of information (besides 500 error) is a new entry in the IIS log:
2012-12-04 13:06:05 127.0.0.7 GET / - 80 - 127.0.0.1 Mozilla/5.0+(compatible;.....)
To verify this, is there a way to check which stage of the pipeline a request failed? Is it possible to run the logging modules before the failure occurs?
There is a trace event logger for HTTP.sys. With this you can determine if the request is even making it to the right app pool in IIS. Direction on usage
As a last resort, Microsoft offers a tool called Debug Diagnostic. When you have no other option, use this. It will produce a crash dump of the app pool of your choice. Not easy to go through, but it’s a lead. Direction on usage
I have created a custom SharePoint web service that was deployed to, and successfully tested on, a test environment. Unfortunately, the web service has since stopped working, and I am trying to determine what the error is.
The web service now returns the following error in the SOAP response:
SOAP:server
Server was unable to process request. Object reference not set to an instance of an object.
There have been no changes to the deployed web service, so I am assuming that a more recent deployment has altered the SharePoint configuration. My web service .asmx is deployed to the _vti_bin folder, and the assembly is deployed to the GAC. I can see the WSDL file being displayed when I browse to http://servername:port/_vti_bin/MyCustomWebService.asmx. The web methods in the assembly make use of logging (to the Windows Event log), but no logging is occurring when I try and access the web service, which suggests that the call is not getting as far as entering the web method.
Given the above, can anyone offer any suggestions as to debug this issue?
Thanks. MagicAndi.
Update
I have now realised that when I consume the web service from the endpoint http://servername:port/Site/_vti_bin/MyCustomWebService.asmx, it works, but when I use the endpoint http://servername:port/_vti_bin/MyCustomWebService.asmx, the web service fails as described above. I will update further when I diagnose the cause of the issue.
this is a try catch to get more infomraion on the exception. It will give you more information which will help debug your problem
try {
// Do soap call here
}
catch (System.Web.Protocols.SoapException soap_ex)
{
Console.WriteLine(soap_ex.Detail.OuterXML);
}
catch(System.Exception ex)
{
Console.WriteLine(ex.Message);
}
The easiest option is to attach a debugger set to break on exceptions. If your infrastructure rules don't allow that, you'll probably need to add some additional logging to your code on the server. If you are lucky there may be enough information available in the soap message, but in my experience null reference exceptions usually need more information to be found easily.