Skip to main content
Solved

Error code: [82:158]

  • Mar 7, 2024 4:07 PM UTC
  • 4 replies
  • 623 views

Hector
Novice
Forum|alt.badge.img+1

Over the last several days my jobs are getting killed on Metallic because of this error [82:158]. Since we’re on the cloud we don't have any control over Media Agent or storage.  Are other customers seeing this problem as well? I’m still trying to catch up on all my EXO backup, but these problem keep making it difficult to do. 

Best answer by dwatcv

For me this ended up being because my Commserve and the client were at different versions. Matching up the release versions such as 11.40.67 to 11.40.67 resolved the problem. I don’t know if your versions are out of phase.

View original

4 replies

Forum|alt.badge.img
  • Novice
  • Mar 7, 2024 8:37 PM UTC

Yeah, I’ve been seeing that the last couple days for a couple customers. Been seeing 82:158, 7:98, 14:274, 13:245, 14:295 and 32:599. So far it hasn’t consistently made any particular backup fail over and over for any of our customers. But I have seen half a dozen issues over the last 2 to 3 days.


Forum|alt.badge.img
  • Novice
  • Aug 19, 2024 9:06 AM UTC

Hi!

Same experiience here.

Anyone ever found a solution for this?


Aplynx
Vaulter
Forum|alt.badge.img+17
  • Vaulter
  • Aug 24, 2024 10:24 PM UTC

I’d suggest opening a support ticket with the metallic team to review if you haven’t already. 


  • Novice
  • Answer
  • Aug 9, 2026 11:34 AM UTC

For me this ended up being because my Commserve and the client were at different versions. Matching up the release versions such as 11.40.67 to 11.40.67 resolved the problem. I don’t know if your versions are out of phase.