In my application parse HTML document by using IHTMLDocument2, EOleSysError exception is raised during creating instance of IHTMLDocument2.
In few days ago, My application worked correctly.
Are there anyone has information about the phenomenon like this ?
My OS is Windows10 (64bit).
This answer follow my comment.
Maybe Security policy about COM had been changed in KB3206632.
I confirmed system log. Event ID 10016 was recorded. So I set appropriate permission by using "regedit.exe" and "dcomcnfg". And finally, My application has work correctly after re-install KB3206632 .
Related
I am facing a weird problem today, when running my MuleSoft application locally from my AnypointStudio and firing a request from postman, I am getting 403 error. When debugging I found out that the application is checking for flowVars._clientName, however it is missing. According to this documentation, actually yes flowVars._clientName is expected.
https://help.mulesoft.com/s/article/How-to-get-the-client-application-name-in-a-flow-based-on-the-client-id-and-client-secret.
So my application fails with 403 error. Seems that other environments are working perfectly fine.
And yes it is using Client Id enforcement.
Any clues?
Without more details it looks like the issue is inside the logic of your application. The KB article that you referenced is a how to in case you need to obtain the client name. It doesn't say that you have to use for authentication. You don't describe how the application does authentication/authorization. Is it in a flow? Or in a policy? If it is the standard Client ID enforcement policy, the expressions to evaluate client id and secret can be configured, but I don't think the default is not #[flowVars._clientName] nor #[flowVars._clientId].
Note that Exchange is basically a repository of APIs and other artifacts. It doesn't authenticate anything at execution time. Unless your application is trying to use it somehow, but I can't think of a reason for that.
The issue was resolved only by re-downloading Anypoint Studio and mule runtime. Very weird, it was happening only for one application, not for the others. Creating a new workspace did not help, deleting the application and re-cloning and installing did not help, even recloning in a new directory did not help. Only using a new Anypoint Studio and runtime installation resolved it (even with the old code base) ...
Does anyone know how to configure NServiceBus (v6.2) using the AzureServiceBusTransport to not attempt to create namespaces?
I'd like to configure NServiceBus the use a connection string which only has permissions to send (the queue's should already be there and if not an error is more appropriate than creation) but whenever I configure it this way I get the following error:
Pre start-up check failed: Configured to create topology, but have no manage rights for the following namespace(s): xxxxxxxxxxxxxx
This error message suggests the functionality is configurable but having looked through the code and the documentation for the mechanism I can't find it.
Many thanks
Adam
Looks like I answered my own question - a bug was raised against the AzureServiceBusTransport and subsequently fixed a little while ago:
https://github.com/Particular/NServiceBus.AzureServiceBus/issues/528
As the bug says upgrading to version 7.1.8 or 7.2.3 and not enabling installers fixes the issue.
I am trying to add Apache Nifi in ambari but continuously failing with error Error occured during stack advisor command invocation:
Unable to delete directory /var/run/ambari-server/stack-recommendations/1.
There is a similar thread with the same error in hortonworks community, I have tried everything mentioned in that thread but unable to fix it. My sandbox is installed in vmware workstation 12 player. I also tried to create and remove directory manually but it is failing with the error invalid argument. Created a thread for this error also on stackexchange. Please help!!!
Here is a link to Hortonworks forum thread. And it seems like sandbox is just broken:
This is due to a docker issue in this 2.5 sandbox build. It will be
fixed in next revision of the sandbox.
There are also some workarounds described (like use older HDP 2.4 or establishing own cluser based on the HDP 2.5 docker image)
Updated sandbox arrived: http://hortonworks.com/downloads
Trust me, active member of community see your posts in multiple locations. In a good, no Big Brother ways :) but cross-posting is an old as world ... Well, you got it.
Did you see a notice for this service in Ambari? Telling it's been deprecated? Same note in the github. There's a good reason for that, it's now been implemented properly by the dev team and with many more features. I.e. all the action is there now.
I think I replied a similar question, though not sure it was yours, take a look in HCC.
I have written an application using MVC4.
After I depolyed it to production, I noticed I get the errors
server could not process you request
from time to time. Its not function related as if I do the same action as before the system works no errors. So I want to find more information about what is causing the issue
how do I log errors in iis 7.5? where should I be looking?
I looked at C:\inetpub\logs\LogFiles\W3SVC2 which is where logging is occuring in my application through iis, but I went through the files and could not see anything that looked like an error..
is there something in particular I should be looking for?
Thanks
Search in SharePoint throws an error, NullReferenceException, whether using the Search box on a normal page or even just loading the Advanced Search page.
I was originally getting System.ServiceModel.ServerTooBusyException and Round Robin Service Load Balancer EndpointFailure errors in the SharePoint ULS logs whenever I tried to search. I examined IIS and determined that the Web Apps existed. I stopped and started the Search Query and Site Settings Serviec on the server. That was the last I saw of the EndpointFailure and ServerTooBusyException errors.
However, a new error showed up. This time is was a System.NullReferenceException from SetPropertiesOnQueryReader() at CoreResultsWebPart.OnInit(). KB Article 976462 looked promising, until further research showed that it adds the AllowInsecureTransport property in the SecurityBindingElement class, and changes the value from its default of False to True. However, this property exists and is already set to True in my environment.
I found this same problem, however deleting the Search Service Apps and Proxies, recreating them and performing an IISRESET did not fix my problem.
When the Advanced Enterprise Search page is brought up, an error is returned to the screen: Object reference not set to an instance of an object.
This is the log entry out of the ULS:
CoreResultsWebPart::OnInit: Exception initializing: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader() at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)
Internal server error exception: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader() at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e) System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader() at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)
Can you have a look at your search topology? Check the status of the following components:
Administration Component
Crawl Component
Query Component
It should be on-line. If it's not, click on Modify Topology and re-provision it.
Navigate to centraladmin:port/_admin/FarmServers.aspx, and check the status of your servers. It should say No action required for all servers - if it says Upgrade required, then run the product and configuration wizard on WFE and app servers depending upon your SP servers.
There may be some rogue entry in your config DB which may be causing this. As you have already re-provisioned search there may be some orphan DB causing the issue. Navigate to centraladmin:port/_admin/databaseStatus.aspx. If you don't see old orphan search DBs here, please delete the search service application, access the above URL again and check if its there. If it is then run the following PowerShell command to remove orphan DBs:
$orphanedDB = Get-SPDatabase | where{$_.Name -eq "MySearchDatabase"}
$orphanedDB.Delete()
I had a similar problem and following Vinod's answer noticed that the "Search Alert Status" in Search Administration was disabled (I intended it to be). Enabling it fixed the issue, meaning that the search pages now render. I was then able to disable the "Search Alert Status" again and the pages continue to work fine.
Hope this helps someone else before they reset / restart services as suggested elsewhere on the web.
I got the same error, restarting SharePoint server fixed my problem.
I just encountered the same problem, and fixed it by:
I verified that the SharePoint Web Services site existed in IIS, and that SecurityTokenServiceApplication existed as a virtual directory.
In my case, I found that the application pool that powered it was stopped due to bad creds. I fixed the creds, bounced the pool, and bounced the site.
That still didn't resolve the issue, so I moved into Sharepoint Central Admin, went to Application Management -> Manage Service Applications.
I clicked on Search Service Application and created a new crawl for my local sites, and did a full index.
Finally I clicked through all of the pieces in the search application topology, changed nothing, but applied topology changes when I was done.
That combination of things fixed it for me.