Server 2005上的AppDynamics数据库代理4.3.10错误

Question

我只是为我的数据库测试AppDynamics，我可以让它在MySQL 5和Server 2014上工作，但是我在Server 2005上发现了一个JDBC错误。

以下是错误日志：

06 6 /controller/instance/DBAGENT_MACHINE_ID/db-monit 2017 00:55:59,461错误AD线程池-Global0 DBAgentPollingForUpdate:30 -连接到URL davinci2017060100542331.saas.appdynamics.com:443或-config/37784: org.apache.http.NoHttpResponseException: davinci2017060100542331.saas.appdynamics.com:443未能响应06 6月2017 :55:59,473警告AD线程池-Global0 DBAgentPollingForUpdate:62 -来自控制器/无法连接的配置请求的无效响应。Msg:连接到URL /controller/instance/DBAGENT_MACHINE_ID/db-monitor-config/37784 06 6月2017 00:56:00,026 INFO -Scheduler-3月收集器时发生致命传输错误:141-DB收集器DBSERVER01暂时禁用。06 6月2017 00:56:01026 INFO -Scheduler-3 ARelationalDBCollector:59 -(Re)初始化DB收集器‘DBSERVER01 01’。06 6月2017 00:56:01 040 INFO -Scheduler-3 MSSqlCollector:74 -获得url jdbc连接:sqlserver://192.168.1.100:1433 06 6月2017 00:56:01 047 INFO -Scheduler-3 MSSqlCollector:139 -sqlserver版本= 9.00.5057.00 ( 2005.0 ) 06 6月2017 00:57:00,025错误-Scheduler-1 ADB收集器:172-错误收集数据库'DBSERVER01‘DBSERVER01’月的错误语法com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java：5696)在com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285) at com.singularity.ee.agent.dbagent.collector.db.relational.mssql.AMSSqlCollectorDelegate.collectDBMSMetrics(AMSSqlCollectorDelegate.java:335) at com.singularity.ee.agent.dbagent.collector.db.ADBCollectorDelegate.collectPerMinute(ADBCollectorDelegate.java:88) at com.singularity.ee.agent.dbagent.collector.db.ADBCollector.collect(ADBCollector.java:156) at com.singularity.ee.agent.dbagent.collector.db.ADBCollector.run(ADBCollector.java:139) at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335) at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236) at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694) at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726) at java.lang.Thread.run(未知来源)

Answer 1

SQL 2005是受支持的，但这是4.3.0版中引入的一个bug。目前有针对受支持客户的此问题的诊断修补程序。一旦我们隔离了问题，修复应该在下一个修补程序级别。如果你想要支持，只要给help@appdynamics.com发电子邮件，他们就能提供帮助。谢谢。