- Veeam Support Knowledge Base
- Damaged unpacked_data.txt File Causes Veeam Guest Catalog Service to Not Start
Damaged unpacked_data.txt File Causes Veeam Guest Catalog Service to Not Start
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
The Veeam Guest Catalog Service fails to start and the Svc.VeeamCatalog.logDefault Location: C:\ProgramData\Veeam\Backup\ file contains an error similar to:
Attribute "LastSyncTimeUtc" was not found under the tree "".
or
Attribute "VmName" was not found under the tree "oib#".
Cause
Solution
To resolve this issue:
- Rename the unpacked_data.txt file to append .old after the file extension (unpacked_data.txt.old).
- Start the Veeam Guest Catalog Service, and a new unpacked_data.txt file will be created.
More Information
The state of the file can be confirmed by going to the Veeam catalog location (default: C:\VBRCatalog\Index\Machines\).
Open the unpacked_data.txt file and confirm it looks like the below. The actual time synced will vary.
LastSyncTimeUtc=07/13/2020 16:13:05.054
####################################################
# Unpacked guest index data of unregistered OIBs options
KeepUnpackedInHours=48
####################################################
# Temporary unpacked guest index data
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.