Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CM 8.0.1 Error encountered, can't complete request; check errors before retrying
- Thread starter Anymol2e
- Start date
AvayaTier3
Technical User
Software corruption. Only Avaya services logins "init" or "inads" can access the software tool needed to resolve that type error.
Call Avaya
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
Call Avaya
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
dialtonebone
Technical User
AvayaTier3 said it best... call support.
EECCR errors should also be in your "list history", just to triple confirm your issue.
EECCR errors should also be in your "list history", just to triple confirm your issue.
AvayaTier3
Technical User
Another option would be to restore xln files from before the station was broke.
This may be hard to determine.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
This may be hard to determine.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
jimbojimbo
Vendor
There is another way. First of all, what is the status of TTI? If on and not 100% translated it can cause this specific type of corruption. Perform a list config all and find the last 'p' port. Display the port to find out the extension (typically an analog device). Disable TTI. See if you can delete the station. Enable TTI. Validate it completes 100%. Disable TTI. Validate it completes 100%. Make sure your System Parameters Maintenance is configured to not save translations if corrupted. Save translations. Schedule a reset system 4 to "clean up" the system.
If this doesn't work, disable TTI. Make sure it completes. Reset System 4 then remove the station. Enable/Disable TTI and verify it completes 100%.
While I've never gotten AT&T/Lucent/Avaya to admit it, TTI can be the root of so many problems. Especially corruption.
There are actually a couple of different ways to corrupt an analog station. Provision had this problem several years ago where input was not validated and the OSSI interface permitted an "A" where an "a" should have been used causing the exact same issue you are experiencing.
Also, if you have gateways/cabinets which have been pulled out but translations are still in the system GET RID OF THEM!
If this doesn't work, disable TTI. Make sure it completes. Reset System 4 then remove the station. Enable/Disable TTI and verify it completes 100%.
While I've never gotten AT&T/Lucent/Avaya to admit it, TTI can be the root of so many problems. Especially corruption.
There are actually a couple of different ways to corrupt an analog station. Provision had this problem several years ago where input was not validated and the OSSI interface permitted an "A" where an "a" should have been used causing the exact same issue you are experiencing.
Also, if you have gateways/cabinets which have been pulled out but translations are still in the system GET RID OF THEM!
- Status
Similar threads