Problems with System State Backup because of Anywhere USB

[mkruege]

We are experiencing systemstate backup-problems of a windows 2008 x64-server with anywhere usb-drivers (V2.70 installed in 2010, updated to V3.51 in the meantime.)
Reviewing the logs it looks like:
https://www.veritas.com/support/en_US/article.TECH76478
Additionally we get snapshot-warnings (file not found) for the followking files:
c:\windows\system32\awusbcon.exe
c:\windows\system32\awusblog.exe
c:\documents and settings\all users\start menu\programs\anywhereusb\anywhereusb release notes.lnk
c:\windows\system32\93009375.txt
c:\windows\system32\awusbcheck.exe
c:\windows\system32\drivers\fwaw2700103.bin
c:\windows\system32\drivers\fwaw2700104.bin
c:\windows\system32\drivers\fwaw2700105.bin
c:\windows\system32\drivers\fwaw2700106.bin
c:\windows\inf\oem11.inf
c:\windows\inf\oem12.inf
c:\windows\inf\oem13.inf

It seems the uninstall did not really cleanup after itself/all references in the system.

Please advise / give instructions on how to manually remove all traces of the old/removed files so SystemStateBackup does not fail anymore.

Many thanks in advance for all efforts!

mik

[jeremym]

It sounds like (unfortunately), you may be running into an old AnywhereUSB installation-related bug, per this KB article:

http://knowledge.digi.com/articles/Knowledge_Base_Article/A-failure-occurred-reading-an-object-error-with-Symantec-Backup-Exec-software

[mkruege]

Thank you very much for your help!
Unfortunately the (digi-)answer to my problem is hard to accept…

[jeremym]

That is certainly understandable.

If you haven’t already, you can try to manually deleting most of those files from the hard drive.

The .inf files may need to be uninstalled through the “pnputil” utility. If you issue the command “pnputil -e > pnputil.txt” that should create a new text file called pnputil.txt (you can actually name it whatever you want) and list all of the currently installed .inf files. Then you could go through them and confirm that the stale ones are 11, 12, and 13. Might want to search for “digi” or “anywhereusb” too. Any .inf files you want to uninstall should be done by “pnputil -u” for example “pnputil -u oemxx.inf” if I recall correctly.

No promises here but this could be worth trying.

[timjohnson2584]

@jeremym

That is certainly understandable.

If you haven’t already, you can try to manually deleting most of those files from the hard drive.

The .inf files may need to be uninstalled through the “pnputil” utility. If you issue the command “pnputil -e > pnputil.txt” that should create a new text file called pnputil.txt (you can actually name it whatever you want) and list all of the currently installed .inf files. Then you could Archerypick go through them and confirm that the stale ones are 11, 12, and 13. Might want to search for “digi” or “anywhereusb” too. Any .inf files you want to uninstall should be done by “pnputil -u” for example “pnputil -u oemxx.inf” if I recall correctly.

No promises here but this could be worth trying

1. Access Webhook Configuration: Log in to the platform or service where you set up the webhooks. This could be a third-party service, an API, or a custom application you built.
2. Locate Webhook Settings: Navigate to the settings or configuration section where you initially set up the webhooks. This is where you can modify the webhook endpoint URL.
3. Update the Webhook URL: Look for the field that specifies the webhook endpoint URL. Replace the staging URL with the desired production or live URL where you want the webhooks to be sent.
4. Save Changes: After updating the webhook URL, save the changes to apply the new configuration.
5. Test Webhooks: Once you’ve updated the webhook URL, test the webhooks to ensure they are now being sent to the correct production URL and properly processed by your application or service.
6. Monitor for Errors: After making changes, monitor the webhook traffic to ensure that there are no issues or errors with the new setup.