I can no longer use the NT Event Log Test using RMA (active). All the tests get 'NT Event Log Tests failing with RMA 301 System Error 1783'. This is across several different RMAs. I do have 1 RMA that still works so I compared all the settings and configurations but I see no difference. As far as I know group policy is the same.
Each RMA is connected to a different NT Domain/Network. The RMA service is logged on using a domain admin account. I've tried using connection manager to help and also setting the account on the test itself with no luck.
NT Event Log Tests failing with RMA 301 System Error 1783
HostMonitor version?
RMA version?
Windows version?
Service Pack?
NT Event Log test mode - NT mode or Vista mode?
Other tests work fine? CPU Usage, Process, Service?
Resource usage on RMA and target systems? Total # of handles, threads, User objects?
>I can no longer use
What exactly was done when test stop working? Windows Update? RMA update?
> All the tests get 'NT Event Log Tests failing with RMA 301 System Error 1783'.
We think such problem was caused by some Windows Update in 2016. Then it was fixed by the following updates..
Microsoft says error 1783 = "The stub received bad data" but does not explain what exactly is the problem and how to fix it. The only Microsoft tip we saw - reduce number of installed services (because the number of services installed leads to some Windows buffer overflow).
Regards
Alex
RMA version?
Windows version?
Service Pack?
NT Event Log test mode - NT mode or Vista mode?
Other tests work fine? CPU Usage, Process, Service?
Resource usage on RMA and target systems? Total # of handles, threads, User objects?
>I can no longer use
What exactly was done when test stop working? Windows Update? RMA update?
> All the tests get 'NT Event Log Tests failing with RMA 301 System Error 1783'.
We think such problem was caused by some Windows Update in 2016. Then it was fixed by the following updates..
Microsoft says error 1783 = "The stub received bad data" but does not explain what exactly is the problem and how to fix it. The only Microsoft tip we saw - reduce number of installed services (because the number of services installed leads to some Windows buffer overflow).
Regards
Alex
RMA 301 System Error 1783
Hello,
We also get this error on our internal servers when checking eventlogs.
Together all have only the server on which the remote agent is located.
This is Server 2019 Version 1809 with all the latest updates as well
8 GB RAM
KS Hostmonitor is version 11.98 on the Monitoring Server with Server 2016
Problem only affects us. There are no mistakes for the customers.
Reboot the monitoring server and the server with RMA Agent did not improve.
Do you have further suggestions here?
Sincerely
We also get this error on our internal servers when checking eventlogs.
Together all have only the server on which the remote agent is located.
This is Server 2019 Version 1809 with all the latest updates as well
8 GB RAM
KS Hostmonitor is version 11.98 on the Monitoring Server with Server 2016
Problem only affects us. There are no mistakes for the customers.
Reboot the monitoring server and the server with RMA Agent did not improve.
Do you have further suggestions here?
Sincerely
Sorry, we cannot find any useful information.
Are you using "Compatibility: Windows NT" mode or "Compatibility: Windows Vista" mode?
Test performed by RMA agent v6.69? started as service? under local admin account?
What means "Problem only affects us. There are no mistakes for the customers"?
("us" and "customers" - different domains? Different servers in the same domain? Different domains monitored by different RMA agents?)
Do you mean 1 RMA cannot check several servers? 1 RMA cannot check any server?
Regards
Alex
Are you using "Compatibility: Windows NT" mode or "Compatibility: Windows Vista" mode?
Test performed by RMA agent v6.69? started as service? under local admin account?
What means "Problem only affects us. There are no mistakes for the customers"?
("us" and "customers" - different domains? Different servers in the same domain? Different domains monitored by different RMA agents?)
Do you mean 1 RMA cannot check several servers? 1 RMA cannot check any server?
Regards
Alex
re
Hi Alex,
sorry for the description..
It seems like it's on Server 2019.
Since my colleague has updated the server on which the RMA is from 2016 to 2019, the problem arises.
I migrated the remote agent to a 2016 server and now the tests are working again.
Remote agents are version 6.65. because Hostmonitor is version 11.98.
He is started as a service.
In summary, if the Active RMA Agent is on a server 2019 then the Eventlog Checks will fail with Error 1783.
sorry for the description..
It seems like it's on Server 2019.
Since my colleague has updated the server on which the RMA is from 2016 to 2019, the problem arises.
I migrated the remote agent to a 2016 server and now the tests are working again.
Remote agents are version 6.65. because Hostmonitor is version 11.98.
He is started as a service.
In summary, if the Active RMA Agent is on a server 2019 then the Eventlog Checks will fail with Error 1783.
re
Hi
Iam Using Windows NT Mode.
I have now tested it on another host monitor system on which the RMA is also on a server 2019.
The same error occurs.
So it's up to Server 2019 in conjunction with RMA 6.65 and NT Eventlog Check... ?
Supplement:
My Workaround is now to Switch to "Vista" Mode and set Logon credentials.
Then it works... hm
Thank's for the Tipps
Iam Using Windows NT Mode.
I have now tested it on another host monitor system on which the RMA is also on a server 2019.
The same error occurs.
So it's up to Server 2019 in conjunction with RMA 6.65 and NT Eventlog Check... ?
Supplement:
My Workaround is now to Switch to "Vista" Mode and set Logon credentials.
Then it works... hm
Thank's for the Tipps
-
hd@miralix.com
- Posts: 14
- Joined: Mon Aug 17, 2009 4:12 am
Problem after upgradering to Windows Server 2019
Hi. We are running HM 11.97. We monitor 30 servers using the test "NT Event Log" with compability "Windows NT mode". All 30 Windows Server 2016 servers was monitored until Saturday when we upgraded 15 servers to Windows Server 2019 including the server running HM. We are able to monitor the 15 servers running Windows Server 2019 but all 15 servers running Windows Server 2016 is giving us problems. We get the "RMA: 301 - System Error. Code: 1783." when testing. NOTE: All other tests (service, temperature and so on works just fine) on both Windows Server 2016 and Windows Server 2019.
-
hd@miralix.com
- Posts: 14
- Joined: Mon Aug 17, 2009 4:12 am
We prefer "Windows NT mode" because "Windows Vista mode" never works. Our Windows Server 2019 that works with "Windows NT mode" fails with "Windows Vista mode" and reports "RMA: 301 - Cannot open event log. The RPC server is unavailable." Out Windows Server 2016 reports "RMA: 301 - Cannot open event log. Access is denied" when using "Windows Vista mode". We've never been able to get "Windows Vista mode" working even though 3 of us have tried and the manual does not help us.
NT mode allows to check only standard (old) channels like Application, Security, System.
- Remote Event Log Management (NP-In)
- Remote Event Log Management (RPC)
- Remote Event Log Management (RPC-EPMAP)
RMA and target systems located in the same domain?
Try to specify account for this test using Connection Manager (HostMonitor menu Profiles->Connection Manager)
Regards
Alex
I think you need to adjust firewall settings on target systems, make sure the following rules enabled (NT mode may work with 1 rule enabled)"Windows Vista mode" and reports "RMA: 301 - Cannot open event log. The RPC server is unavailable.
- Remote Event Log Management (NP-In)
- Remote Event Log Management (RPC)
- Remote Event Log Management (RPC-EPMAP)
RMA agent is running as service under admin account?Windows Server 2016 reports "RMA: 301 - Cannot open event log. Access is denied"
RMA and target systems located in the same domain?
Try to specify account for this test using Connection Manager (HostMonitor menu Profiles->Connection Manager)
Regards
Alex