8.4 - JetError -1085, JET_errTempPathInUse

[sumeet]

#Split from 8.4 - Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

We have upgraded just one setup (out of 30+) to v8.4 and woke up to this error.

I started the job now and it seems to be fine. Not sure if I should still do the above steps or not.

Will appreciate if Veeam team knows the cause.

Assuming there are hundreds of customers using Veeam Data cloud - I would assume that it would have been upgraded to v8.4 too and this would have been observed.
Or if this error is specific to JetDB, then maybe not in VDC

[sumeet]

For the same job and repository (which is JetDB), had this error on 25th May night, and now yesterday night this Index (zero based) error

[25.05.2026 21:00:03.061] 239 (1) [Info] Invalid repository status is returned (repository ID: 17b90c28-abbc-4a9b-be3f-9fbcf0324009, is outdated: False, is out of sync: False, is out of order: True, out of order reason: JetError -1085, JET_errTempPathInUse, Temp path already used by another database instance)

[Mildur]

Hi Sumeet,

I moved your two comments to a new topic.

In the other topic, the immediate solution was to clear the NATS cache. However, I cannot confirm the root case, because the case was closed after the issue was resolved by clearing the NATS Cache. For a proper investigation, the case should have been escalated to QA, which unfortunately did not happen.

Since that solution or workaround involved NATS, I do not think the same approach will work for Jet databases. Also, you are receiving an error message from the Jet database engine (JetError -1085), which according to Microsoft means:

Extensible Storage Engine Error Codes

JET_errTempPathInUse
-1085
The path to the temporary database is already being used by another database instance.

Please contact our customer support team so we can investigate your error further.
And don't forget to provide us with the case number.

Best,
Fabian