When I check the windows update event logs I found this error.
of " WU operation (CSearchCall::Init ID 613, operation # 4370) stopped; does not use network; is at background priority)"
Can anyone explain the reason for this issue and how to fix this?
Related
My Sql developer was working fine from long time, suddenly from yesterday when i am trying to reconnect it is giving me following error:-
Status : Failure -Test failed: IO Error: Got minus one from a read call, connect lapse 62991 ms., Authentication lapse 0 ms.
Things I tried to solve the issue:-
Made corresponding changes in sqlnet.ora , listener.ora and tnsnames.ora files
Checked is there are too many open connections to the database service.
Restarted ORACLE service and listener
Firewall related changes
Reinstalled ORACLE
In my case the issue, it is due to a malware. Whenever i am trying to connect to DB port, it was automatically getting changed by malware.
You can also identify the problem by using lsnrctl status command, for further information. You can also see the log file of listener.
Run a full scan on your machine and restart listener, hope that helps.
In SAP HANA index server and statistics server stopped suddenly and not running.
I tried to stop and restart the server by the following commands.
HDB stop
HDB start
But still it is not working. Does anyone know what causes this problem and what is the solution? Thanks in advance.
If the indexserver doesn't start, you cannot logon as SYSTEM (or any other user for that matter). A good way to find out what the reason for the failed start is to check the tracefile for the nameserver, the indexserver and the statisticsserver.
Logon as <sid>adm and change to the tracefile folder via cdtrace.
Then find the tracefiles and use e.g. less to read through them to find the actual error messages.
Alternatively you can use SAP HANA Studio with the emergency connection to review the trace files without terminal access.
I am trying to install nservice bus on a fresh win server 2012 box and things are not working properly. Any help is appreciated..
I get setup failed prematurely and when I dumped into log file.. this is the error I get..
Calling custom action NServiceBus.Wix.CustomActions!NServiceBus.Wix.CustomActions.CustomActions.InstallMsmq
Installing/Starting MSMQ if necessary.
CustomAction InstallMsmqAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 16:36:36: InstallFinalize. Return value 3.
Action 16:36:36: Rollback. Rolling back action:
Do I have to manually add MSMQ features.?
Yes you need to enable the MSMQ features first.
BTW, the MSI is really only to be installed on developers machines, to prepare a machine in production use the powershell cmdlets, see http://docs.particular.net/nservicebus/managing-nservicebus-using-powershell
Is your dev machine a WinServer 2012?
I have an exsiting application that works fine on a windows 2003 server. I having been moving it to windows 2008r2 and when the application trys to access the queue it gets the below error? The Indentity user of my app pool has full control of my message queue. Does anyone have any ideas on how to fix this. I believe this to be server config issue.
[MessageQueueException (0x80004005): Access to Message Queuing system is denied.]
System.Messaging.MQCacheableInfo.get_ReadHandle() +221
System.Messaging.MessageEnumerator.get_Handle() +70
System.Messaging.MessageEnumerator.MoveNext(TimeSpan timeout) +93
System.Messaging.MessageQueue.GetAllMessages() +58
NServiceBus.Unicast.Subscriptions.Msmq.MsmqSubscriptionStorage.Init(IList`1 messageTypes) +124
NServiceBus.Unicast.UnicastBus.Start(Action`1[] startupActions) +674
Connector.Service.InitBus() +201
Connector.OutgoingService..cctor() +9
I just had the same experience when moving from Win 2003 to Win 2008 R2 - and it turned out that 2008 R2 create queues with lowercase letters when I use the .NET APIs to create the queue. Later when the application tries to access the queue it cannot access them (giving the error you state) using uppercase letter. Using lowercase solves the problem.
/AZ
I also got the following:
System.Messaging.MessageQueueException (0x80004005): Access to Message Queuing system is denied. Being generated from: NServiceBus.Utils.MsmqUtilities.
Giving 'Everyone' permissions on the 'error' queue solved the problem.
I also use 2008 R2, Yes, the actually queue name being created is lower-cased, but in my code, access it using the Upper case works well.
Also added permission to 'Anonymous Logon' and it worked.
I am making my first attempts at using PowerShell remoting features. I've set up the "destination" server using the instructions in the help docs. But when I attempt to start a remote session (by executing an "Enter-PSSession servername1" command), it sits there for a long time, and eventually gives this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.
I also noticed that while it was sitting there, my computer's performance had degraded. Looking at Task Manager, I see that ekrn.exe, which is the kernel process for Nod32 Antivirus, was using a lot of CPU (~50%, sometimes edging higher). It seems to never stop using the CPU until I kill the process, and I did some testing, and it clearly begins to use all that CPU as soon as I execute that Enter-PSSession command.
I then tried disabling the Nod32 anti-virus, executed the same command, and voilà, it worked, and the remote session started properly.
But obviously disabling my anti-virus isn't a solution. Can anyone suggest a better one?
It turns out I wasn't running the latest version of Nod32. I was running version 3, the I was able to upgrade to version 4, and the problem went away.