11-17-2017 10:25 AM
Hi - I just upgraded from SSR 2013 R2 to 16. I feel right at home except that the email notifications are a pain. They've gone from simple, readable messages like this:
Date: 11/17/2017 1:29:23 AM
Notification Type: Info
Priority: High
Description: Info 6C8F1F7E: A scheduled incremental recovery point of drive F:\ was created successfully.
to this:
Date: 11/17/2017 4:02:24 AM
Notification Type: Info
Priority: High
Description: Result (0x6c8f1ff2 34 VPRO_INFO_SCHEDULED_BACKUP_INC_JOB Args [1] Arg (0xbab000d 24 Full Backup - All Drives);)<9 1.0-*-*-* >
Can they be changed back, or failing that, can I get a glossary somewhere so I can at least figure what the heck it means?
Solved! Go to Solution.
12-04-2017 08:38 AM
It's a cosmetic issue - there is no loss to features or functionality.
11-20-2017 12:21 AM
Please try this solution: http://www.veritas.com/docs/100033361
11-29-2017 06:20 AM
Did that article help?
11-29-2017 11:56 AM
nope, sorry. still look like this:
Date: 11/29/2017 11:54:17 AM
Notification Type: Info
Priority: High
Description: Result (0x6c8f1f63 29 VPRO_INFO_MANUAL_BACKUP_START Args [1] Arg (0xbab000d 24 Full Backup - All Drives);)<9 1.0-*-*-* >
11-30-2017 12:39 AM
So I assume the registration of the DLL was successful?
If yes, you may need to open a support case to get this fixed.
12-01-2017 11:48 AM
yes, the DLL registered. I stopped the service, registered the DLL, saw the success message, restarted the service, tested, no joy. Rebooted, tested, still no joy.
First, is this the way the messages are supposed to look now?
Second, if not, what's flipped? some kind of debugging flag?
Thoughts?
12-04-2017 01:16 AM
First, is this the way the messages are supposed to look now?
No, they are not supposed to look like this.
Second, if not, what's flipped? some kind of debugging flag?
This is usually caused by that DLL not being registered correctly. Something is wrong here... I think a support case needs to be opened in order to correct this.
12-04-2017 08:13 AM
OK - thanks for the clarification. Is it a cosmetic issue or a sign of something further wrong? If it's just cosmetic, I may live with it, if not, I will try again with the registration, and failing that, maybe a reinstall. If that doesn't do it I'll open a case.
12-04-2017 08:38 AM
It's a cosmetic issue - there is no loss to features or functionality.
12-04-2017 08:48 AM
OK - thanks!