"API Version is: 4.11 000-00 0" What is the reason for this?

[khoppe]

Hello,

does anybody know where the Log entry "API Version is: 4.11 000-00 0" may come from?

Complete log entry: DEBUG [mksis.IntegrityServer] DEBUG(0): [http-exec-114] API Version is: 4.11 000-00 0

We are running 10.4 on server (Build 10.4.0.4301 or other API: 4.12.4301)

I know such a behaviour from a not-well configured Jenkins, if a plugin is used from a higher version than the Integrity server supports.

Does the same happen vice versa (=> plugin of a lower version than running the server) ?

And second question: Is there any possibility that I can find out, WHO is the reason for that entries,

maybe by extended logging or something else?

From our logger.properties:

mksis.logger.message.includeCategory.DEBUG=3

mksis.logger.message.includeCategory.DIAGNOSTIC=10

mksis.logger.message.includeCategory.WARNING=10

mksis.logger.message.includeCategory.GENERAL=10

mksis.logger.message.includeCategory.ERROR=10

mksis.logger.exception.includeCategory.DEBUG=3

mksis.logger.exception.includeCategory.DIAGNOSTIC=10

mksis.logger.exception.includeCategory.WARNING=10

mksis.logger.exception.includeCategory.GENERAL=10

mksis.logger.exception.includeCategory.ERROR=10

Every hint would be helpful.

[mrump · Accepted solution]

Maybe you could turn on the API logging, to get more info.

mksis.logger.message.includeCategory.API=10

mksis.logger.exception.includeCategory.API=10

Possible candidate are:

- any plugin you may use (Word, Excel, MS Project, Visual Studio, Eclipse, ....)

- any custom tool you may use

who's implementation is based on an older version of the API.

As the API should be mostly backward compatible and all you see is a log entry, I wouldn't worry that much.

HTH Matthias

[khoppe]

Hello,

I'm less afraid that I get problems from single requests of that kind, I'm more afraid about hundreds and more log entries of that kind. Since we've had in the past trouble with bad configured Hudosn- and Jenkins-Installations, AND since I faced similar entries from that, I'm wondering whether there are some more possibilities to detect root caise of them.

API Logging didn't help.

Is there any possibility existing to find out:

- Which tool causes these entries?

- From which computer these requests come from ?

- Which User ID is used for it ?

It would be helpful to get answers for at least one of these questions.

[KaelLizak]

Hello Klaus,

As Matthias mentioned, this could come from plug-ins or custom tools.

This message seems to indicate that the API is being accessed using an older jarfile than the 10.3 jarfile. Look throught the applications you have, with a particular eye towards older applications/plug-ins which have not been updated in some time.

As Matthias mentioned, this should not be a significant issue, since the API is designed to be backwards compatible.

Enabling thread logging may help, since you can then tie together messages with the same thread ID in the server.log to try to track down what tool is issuing this message, and what User ID it ties to (based on login messages). Tracking down the computer requires a little more inference and ingenuity, but is also possible.

Regards,
Kael