Hi Symantec
Refering to the article I post to Symantec below, I have experienced identical issue in TECH216099 on my BE2014 that is with same error message from BE2012 customers and when I log a support case they advise this is BE2014 product so I have to do the troubleshooting from scratch again as the issues is for BE2012. I have sent them the logs and advise the log level is not enough so I have to restart the painful debugging process and wait for issues reoccuring and going backward and forward with Symantec support that can take another months.
In this forum link below: Symantec also response: 1) TECH 216099 was written for BE 2012 and may not apply to BE2014 (and probably will not be fixed in BE 2012)
https://www-secure.symantec.com/connect/forums/dup...
My concern is if the issues is not fixed in BE2012 and the issues is carried on to BE2014. Now I have to restart all the troubleshooting and log collection with Symantec as they already have enough information to open the TECH216099 with BE2012. Also in the past for another TECH201425 that has been opened for almost 2 years, I am facing the same issues. I call up with Symantec support, report the issues that I find is identical to the TECH201425 has been identified is a known issues not yet fix in BE2012 (SAME SITUATION TO THIS ONE). The Symantec support insist to do a log collection and go through a lengthly process for the debug, troubleshooting for weeks and without update until I push to Baseline Engineer and Duty Manager. Over the phone they then admit the issues not yet fix in BE2012 has been carried over to to BE2014. I have to insist the to update the product to included BE2014 and it take almost a month for them to update the TECH201425 to include BE2014 as affected product.
https://www-secure.symantec.com/connect/forums/whe...
Now for TECH216099 I have to go through the same process again??? Isn't this is a known issues already without fixing it by Symantec in previous version BE2012 that probably will not be fixed and the issues is now been carried over again to BE2014? Why symantec customer has to suffer twice to go through the lengthly and painful symantec support process since a TECH216099 has been issues and is understand investigation by Symantec. It has been pending for outcome of the investigation according to the article for past 7 months. What is the outcome of the investigation?
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.
Regards,
Ag BC