AdtServer

Hi,
After i installed and configure Audit collection server on SCOM 2012 sp1 and attempting to generate report from audit collection in scom but this issue occurred
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'dataSet'. (rsErrorExecutingCommand)
Invalid object name 'AdtServer.dvAll'.
thanks in advance

This info might help..
Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run.
Microsoft.Reporting.WinForms.ReportServerException: An error has occurred during report processing. (rsProcessingAborted) ---> Microsoft.Reporting.WinForms.ReportServerException: Query execution failed for dataset 'allResourceAttributeDisplayNames'. (rsErrorExecutingCommand)
---> Microsoft.Reporting.WinForms.ReportServerException: Invalid object name 'AdtServer.dvOldResourceAttributes'.
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.GetParameters()
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.Initialize(ServerReport serverReport)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args)
Microsoft.Reporting.WinForms.ReportServerException: Query execution failed for dataset 'allResourceAttributeDisplayNames'. (rsErrorExecutingCommand) ---> Microsoft.Reporting.WinForms.ReportServerException: Invalid object name 'AdtServer.dvOldResourceAttributes'.
--- End of inner exception stack trace ---
Microsoft.Reporting.WinForms.ReportServerException: Invalid object name 'AdtServer.dvOldResourceAttributes'.

Similar Messages

SCOM 2012 R2 Post upgrade issues

Hey all,
yesterday we upgraded our SCOM environment from 2012 SP1 to R2. All of the installers ran fine without any issues. After a couple reboots it was back up however we have run into some issues.
Issue 1: The ACS seems to be broken. I can usually run a query on the ACS database manually and get back audit entries. However, now I am getting nothing back at all. Here are the errors that are repeated every few minutes on both
management servers. I did run the ACS upgrade on them both yesterday.
Error occured on database connection:
Status: 0x00040000
ODBC Error: 14
ODBC State: 01000
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (ParseConnectParams()).
Database: Register
Connection: ComplianceTest
Statement: -
Error occured on database connection:
Status: 0x00200001
ODBC Error: 14
ODBC State: 08001
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
Database: Register
Connection: ComplianceTest
Statement: -
Issue 2: Our UNIX agents are all greyed out now and when I try to upgrade them I get the following error.
EDIT: and here is something else I just found on our other management server
Any info would be great
Thanks
Warm Fuzzies!

I am going to update this post. The service is still crashing nightly. The views dvAll, dvAll5 and dvHeader are not being created. I tried the fix provided by the Microsoft rep and it did nothing. I have uninstalled and reinstalled
the ACS server multiple times and the views are never created. When I start the ACS services I get the same errors.
AdtServer encountered the following problem during startup:
Task: Load Certificate
Failure: Certificate for SSL based authentication could not be found. SSL authentication will be disabled
Error: 0x00000002
Error Message:
The system cannot find the file specified.
Error occured on database connection:
Status: 0x00040000
ODBC Error: 4624
ODBC State: 01000
Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.
Database: SqlWriter
Connection: Maintenance
Statement:
I see where the forwarders are connecting. No other errors or messages. The service is set to start up as the Network Services account. The DOMAIN\SERVER$ has a logon and is mapped to the SQL user AdtServer on the OperationsManagerAC database.
We have almost a terabyte of data that we cannot get to after the R2 upgrade.
Very frustrating!!!!
Warm Fuzzies!

Error Starting Adtser service [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '!'.

Been fighting ACS upgrade issues since we upgraded to R2. Every night the ACS service fails. When I start it back up I get the following error.
It looks like the DbCreatePartition.sql and/or DbDeletePartition.sql scripts are not running as we have a lot of views prefixed dvAll, dvAll5, etc. but no actual view of this name as is supposed to be and reports for user activity are throwing an error.
I have done everything I can find on the blogs, but nothing is helping. We have almost a terabyte of data in this database and reinstalling a new database is 99% out of the question.
I dont know if its permission related or not, but I am up to here with this ACS server.
Any help would be great, thank you
Warm Fuzzies!

Hi,
If Event 4618 is logged when the updating process sets permissions on certain stored procedures.
You can safely ignore event 4618 in this scenario.
Here is more details, please refer to the below link:
Event 4618 is logged when you use the AdtSetup.exe program to update an Audit Collection Services installation in System Center Operations Manager 2007
http://support.microsoft.com/kb/949452/en-us
And if the event indecate logon failed, then the below article could be helpful:
http://blogs.technet.com/b/jonathanalmquist/archive/2008/03/13/adtserver-event-id-4618-logon-failed.aspx
AdtServer Event ID 4618 - Logon Failed
Regards,
Yan Li
Regards, Yan Li

SCOM 2012 ACS agent Failed connecting to collector

Hi,
We are using SCOM 2012 on Windows 2012, when installing the SCOM agent with Audit Collection Services the ACS forwarder will report in as healthy until reboot, after reboot the forwarder state changes to failed to connect to collector. (XXX's are redacted
system information).
Forwarder unsuccessfully tried to connect to the following collector(s): XXXXXXXX:51909, status: 0x80090322 (TCP connect), source: registry addresses tried: XXX.XXX.XXX.XXX:51909 If the list of collectors is blank, then AdtAgent was unable to locate a collector.
Common reasons for this message are: The machine(s) listed is not online AdtServer is not running on the machine(s) listed AdtServer on the machine(s) listed is not listening on the specified port TCP connectivity to the AdtServer machine is blocked by firewall,
IPSec, or other filtering mechanism AdtServer on the machine(s) listed actively refused the connection (due to policy or current activity load) For detailed failure information, enable trace logging using the TraceFlags registry key and examine the AdtAgent.log
in the \temp subdirectory of the Windows directory.
Enabling trace logging repeats the same error, unable to connect to server. We have verified, the IP is correct, the FQDN is correct and has a forward and reverse lookup record. We have also verified via telnet that port 51909 is open in both directions.
Any help would be appreciated.

If you are 100% sure port 51909 is open at Collector's side (you don't need to open it on ACS forwarder) and there's no additional firewall somewhere at the middle use wireshark and capture what's going on.
--- Jeff (Netwrix)

ACS Certificate import failure

Hello All,
trying to get a certificate imported on an ACS collector. The import (apparently) fails with this:
>> 1 certificates found for server authentication usage.
>> Enter the number of the certificate you want AdtServer to use for authenticating
>> to AdtAgent or 0 to quit without saving: 1
>> Certificate 1 selected. Attempting to save thumbprint to registry ...
>> failure.
No errors, no messages, no event logs - no nada. I'm not even sure the import actually failed (how to verify ??).
Anyone happen to have an idea on how to troubleshoot this? I tried tracing registry access with Sysinternals ProcMon, but nothing interesting really stood out.
Thx in advance for help and/or pointers!
Rgds - M.

Hi,
here you can find more information how to configure certificates for ACS forwarders and collectors:
How to configure Audit Collection System (ACS) to use Certificate based authentication,
How to Configure Certficates for ACS Collector and Forwarder
Regards,
Ivan

ACS forwarding from untrusted domain 0x80090325 SEC_E_UNTRUSTED_ROOT

I have SCOM 2012 R2 Update Rollup 4 installed with 2 management servers running WS12R2 in a single management group in my main AD domain. One of the management servers is also an ACS collector. I have an untrusted AD domain, with a SCOM gateway server in
it, and I used the gateway to install a SCOM agent on a domain controller in that domain. Now I am trying to configure an ACS forwarder on that untrusted domain controller to talk to the ACS collector back on the management server.
However, when I restart the
Microsoft Monitoring Agent Audit Forwarding service on that domain controller, I get this error in its
Event Viewer > Apps and Services > Operations Manager:
1/23/2015 5:08:01 PM Source AdtAgent Event ID 4369 Forwarder unsuccessfully tried to connect to the following collector(s):
<acsCollectorFQDN>:51909, status: 0x80090325 (TCP connect), source:registry addresses tried: <IP>:51909. If the list of collectors is blank, then AdtAgent was unable to locate a collector. Common reasons for this message are: The machinef(s)
listed is not online. AdtServer is not running on the machine(s) listed. AdtServer on the machine(s) listed is not listening on the specified port. TCP connectivity to the AdtServer machine is blocked by firewall, IPSec, or other filtering mechanism AdtServer
on the machine(s) listed actively refused the connection (due to policy or current activity load). For detailed failure information, enable trace logging using the TraceFlags registry key and examine the AdtAgent.log in the \temp subdirectory of the Windows
directory.
I followed these two articles in order to set up the ACS forwarder on the DC in the untrusted domain: "How to configure security events collection by using Audit Collection Services from computers in untrusted environment?" {1/3/12}https://gefufna.wordpress.com/2012/01/03/how-to-configure-security-events-collection-by-using-audit-collection-services-from-computers-in-untrusted-environment/ "Forwarder
is unable to connect to collector Event id 4369 in forwarder event view" {5/5/14}
http://jimmy-scom.blogspot.com/2014/05/forwarder-is-unable-to-connect-to.html
EXTRA INFO Here are the detailed steps that I took (sorry for all this, but there are an awful number of steps!):
1) I confirmed that the agent for the DC shows as Healthy in OM Console > Monitoring > Operations Manager > Agent Details > Agent Health State > Agent State (right) pane.
2) On the ACS collector, I stopped
Operations Manager Audit Collection Service, then from Admin cmd prompt I did this:
c:> cd \windows\system32\security\adtserver
c:> adtserver –c
} 1 certificates found for server authentication usage.
Enter the number of the certificate you want AdtServer to use for authenticating to AdtAgent or 0 to quit without saving: 1
Certificate 1 selected. Attempting to save thumbprint to registry ...
success.
Then I started
Operations Manager Audit Collection Service.
3) On the DC in the untrusted domain, from Admin cmd prompt I did this:
c:> cd c:\windows\system32
c:> adtagent -c
} No Issued To Issued By Expires
Thumbprint
1: <untrustedDCfqdn> <untrustedDomainCA> 2015-11-30 02:44:58 <thumbprint>
2 certificates found for client authentication usage.
Enter the number of the certificate you want AdtAgent to use for authenticating to AdtServer or 0 to quit without saving: > 1
} Certificate 1 selected. Attempting to save thumbprint to registry… success.
4) On the DC in the untrusted domain, I opened mmc > Certificates > Local Computer > Personal > Certificates > I exported the certificate from step 3 to a DER encoded binary X.509 (.CER) file.
5) I also looked at the Certification Path for the certificate, and figured out which certificate is its Root CA certificate. I copied that certificate to a DER encoded binary X.509 (.CER) file.
6) I copied the first .CER file to a computer in my main domain, which is at 2012 R2 level. From AD Users and Computers, I created a "dummy" computer object using the NetBios name of the DC back on the untrusted domain. I right clicked the computer
object > Named Mappings > I added the .CER file, and left "Use Subject for alternate identity" checked. I unchecked "Use Issuer for alternate security identity".
7) I copied the Root CA certificate .CER file over to the SCOM management server that doubles as my ACS collector, and from there I did mmc > Certificates > Local Computer > Trusted Root Certificates > Certificates > I imported the Root
CA certificate.
8) I also went to my CA server on my main domain, I ran pkiview.msc > right clicked “Enterprise PKI” > Manage AD Containers > NTAuthCertificates tab > and I imported the Root CA certificate there as well.
9) I ran telnet from the DC on the untrusted domain, and confirmed that port 51909 is open from there to the ACS collector on the main domain.
10) I enabled audit collection fot the DC on the untrusted domain. I did this from OM Console > Monitoring > Operations Manager > Agent Details > Agent Health State > Agent State (second column in middle pane) > I selected the Healthy <untrustedDCfqdn>
> I clicked Enable Audit Collection.
Then under "Task Parameters" > i clicked [Override] > for New Value I specified <ACScollectorFQDN>. For task credentials I specified Other account, and specified a domain admin account in the untrusted domain. The result was "The
task completed successfully. Enable Audit Collection, status:Success".
11) On the ACS collector, I restarted Operations Manager Audit Collection Service. On the DC in the untrusted domain I restarted Microsoft Monitoring Agent Audit Forwarding service.
12) Result was this error on the DC in the untrusted domain, in its
Event Viewer > Apps and Services > Operations Manager
1/23/2015 5:08:01 PM Source AdtAgent Event ID 4369 Forwarder unsuccessfully tried to connect to the following collector(s):
<acsCollectorFQDN>:51909, status: 0x80090325 (TCP connect), source:registry addresses tried: 10.1.1.91:51909. If the list of collectors is blank, then AdtAgent was unable to locate a collector. Common reasons for this message are: The machinef(s)
listed is not online. AdtServer is not running on the machine(s) listed. AdtServer on the machine(s) listed is not listening on the specified port. TCP connectivity to the AdtServer machine is blocked by firewall, IPSec, or other filtering mechanism AdtServer
on the machine(s) listed actively refused the connection (due to policy or current activity load). For detailed failure information, enable trace logging using the TraceFlags registry key and examine the AdtAgent.log in the \temp subdirectory of the Windows
directory.
13) On the DC in the untrusted domain I created DWORD reg value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AdtAgent\Parameters\TraceFlags and set it to 524420 decimal. The resulting c:\windows\temp\AdtAgent.log file only confirmed that I'm getting 0x80090325 errors.
After all this, why am I getting 0x80090325, which translates to SEC_E_UNTRUSTED_ROOT ??? Did I do something wrong in steps 5, 7 and 8? Thanks for reading all the way through :)
Marko

Thanks Yan Li, you gave me an idea. I got the ACS forwarder in the untrusted domain to work (!), by analyzing the setup on the SCOM gateway that I set up in the untrusted domain. I issued the ACS forwarder a certificate from the domain that SCOM is in, INSTEAD
of configuring the ACS forwarder to use the certificate that it already had from its own domain.
So the new procedure is: do steps 1 and 2, then instead of step 3 I did this…
2B) I issued a certificate from the AD domain containing SCOM to the domain controller in the untrusted domain that is my ACS forwarder. I did this from the AD Certificate Services web site, and asked it to use certificate template that I created for the
SCOM gateway server in the untrusted domain.
2C) The new certificate appeared in the Personal store of the domain controller. I exported it, then ran the MomCertImport utility so that I would not get an error in the next step (per
http://www.systemcentercentral.com/scom-deployment-across-multiple-networks/)
3) On the domain controller in the untrusted domain, I re-ran "adtserver -c", and selected the new certificate.
3B) I then ran “MomCertImport /Remove”, since I already have a SCOM gateway in the untrusted domain.
Then I proceeded with steps 4, skipped 5, did 6, skip 7-8, did 9-11, result was this on the DC in the untrusted domain, in its Event Viewer > Apps and Services > Operations Manager
2/3/2015 12:20:01 PM Source AdtAgent Event ID 4368 Forwarder successfully connected to the following collector:
<ACScollectorFQDN>:51909, status: 0x0 (success), source: registry
addresses tried: <IPaddress>:51909
ACS forwarding works now! I will confirm by repeating the procedure for another domain controller in the untrusted forest.
Marko

Couldn't connect to collector

Installed fresh Network Monitor ver 1.2.00197 on a win 2008 R2 64 bit server (with service Pack 2 and all updates) - no errors in installation, opened the web-interface and attempted to add windows servers and smart switches. All attempts to add devices return "couldn't connect to collector" error. Verified that the SNMP feature IS installed on the server and was active. Looked at the collector.log file (and others) and could not find any error messages (the windows Application/System logs were also clear.)
Any suggestions? Is there a possible java version issue? (I'm running Java 7, update 40).
Thanks!
Bob Engimann
P.S. - I have a log bundle if you are interested.
This topic first appeared in the Spiceworks Community

Hi Yan Li, thanks for responding.
The certs are not expired yet on Collector and Forwader. And agents would be approved automatically by RMS.
I did restart adtserver service on the collector ,do "adtagent -c" command and restart the adtagent service on forwarder.
But the problem still there. Error is still the same: ConnectToServer():
Calling Disconnect() with error 0x00002746.

AdtServer

Similar Messages

Maybe you are looking for