Instrumentation is not available
What does it mean when I have the following message: "The Agent is connected, but Instrumentation is not available." How do I correct this problem. I am using dynaTrace 5.0.0.3772.
Regards,
Anoh Brou
I have the same problem but with the version 6.0.0.7023.
Here is a related error:
2015-02-13 10:53:02 [00000038] info [native] Sending log files (including previous)
2015-02-13 10:53:02 [00000038] info [native] Exception occurred while listing special logfiles: Exception java.lang.NoClassDefFoundError: com/dynatrace/diagnostics/agent/sysinfo/JvmErrorLogHarvester
Regards,
Octavio López S.
Can you look at the log file of this agent?
Here is a related error amongst others: "2013-01-07 09:31:04 SEVERE ThrowableHandler Uncaught exception in thread "Processing Repository Measurement Data-Thread-50@main": Cannot find the object "measurement_temp2" because it does not exist or you do not have permissions.: com.dynatrace.diagnostics.util.modern.ThrowableHandler uncaughtException:50
com.dynatrace.diagnostics.server.shared.exceptions.repository.UncategorizedRepositoryException: Cannot find the object "measurement_temp2" because it does not exist or you do not have permissions.
at com.dynatrace.diagnostics.repository.exceptiontranslators.DefaultExceptionTranslator.doTranslateException(SourceFile:123)
at com.dynatrace.diagnostics.repository.exceptiontranslators.SQLServerExceptionTranslator.doTranslateException(SourceFile:76)
at com.dynatrace.diagnostics.repository.exceptiontranslators.DefaultExceptionTranslator.translateException(SourceFile:76)
at com.dynatrace.diagnostics.repository.statement.DefaultStatementExecutor.writeOnTransactionalConnection(SourceFile:77)
at com.dynatrace.diagnostics.repository.handlers.DefaultMeasurementHandler$8.run(SourceFile:1069)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)"
--------------------------------------------------------------
What does it mean?
Regards,
Anoh Brou
actually that entry from the server log file indicates a problem with the performance warehouse, not with the agent.
can you take a look at the agent and potentially collector log files. there should be more information.
best,
Christian
not sure, which agent you are referring to, but e.g. for the logfile
dt_EJ_ACPT_SUNONE_Agent_6283.log
you see
2013-01-07 04:06:56 00000001 warning native Unable to register with Server nsfvas02.ad.nsf.gov:9998, CONTINUING WITHOUT INSTRUMENTATION.
which means that at 04:06:56 there was no collector/server available for instrumentation.
at 08:26:36 the collector/server was available and so the agent connected. so it ended up connected but uninstrumented.
best,
Christian
I'm reasonably sure I know what the problem is. This looks like you've created a case sensitive SQL Server PW. The PW needs to be installed/configured as case INSENSITIVE.
Can you check your PW properties please?
Rob
I am not sure that the error is there. The result of "SELECT DATABASEPROPERTYEX('dynaTrace', 'Collation') SQLCollation;" is SQL_Latin1_General_CP1_CI_AS. The CI indicates Case Insensitivity.
Hmmm. Yes, CI is definitely case insensitive, so in this case it seems that error message was a red herring. Note that I normally don't see the "AS" (accent sensitive) in the collation definition, but I don't think that would cause the problem we're seeing.
Rob
Is this a brand new installation, or is this an installation that was previously working that now is not? Looking at your server log, I also saw that there is a PK-related issue:
Violation of PRIMARY KEY constraint 'PK_measurement_high'. Cannot insert duplicate key in object 'dbo.measurement_high'.
So maybe this is a permission problem. Can you look at the schema and see of the table measurement_temp2 is in fact there? You may need to work with support. It seems like the PW database is in some weird state.
No. This is an existing installation. Everything was working great when I signed off on Friday.
Tables measurement_high and measurement_temp2 currently exist in the database.
Regards,
Anoh Brou
I think you should contact support then. I don't want to risk guessing things here on the forum if this is an existing installation that used to work. There seems to be some sort of access issues (permissions change maybe?) to those tables, and I don't like the constraint violation either. That, too, could be a permission thing (for example, perhaps you lost the ability to delete data from a table and now that's resulting in the unique constraint violation.
Sorry I couldn't be of more help.
