Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: tjansen on December 28, 2020, 10:25:51 AM
-
I have an analog line that somehow got redundancy applied to it. It has a Home Element and a Secondary Element. I am trying to delete this extension however it will not allow me to do that without removing the redundancy.
When going to User and Services Configuration the Secondary Element is grayed out and I cannot change it.
Is there a maintenance command that I can use to remove it or delete the extension?
Thanks
-
You will need to go in SDS debug mode to fix this.
-
delete from the primary not the secondary.
-
@sunspark - I have been trying to delete off the primary controller but it wont let me because the analog line is is resilient somehow.
@august - I will look into that and see what I can do
Thanks for the replies, I will try and update if I figure it out.
-
what is the error message when you try to delete it ?
-
I attached the pictures of the error and log also.
Error when deleting the analog line is:
"Changing device number and hosting information at the same time is not allowed."
The Maintenance/Software logs:
Log Type Software
Log Number 1246
Severity Warning
Date 2020/Dec/29
Time 08:56:56
Source DEI Storage Adaptor class
Description updateDEIRecordIndication()->m_adaptorWithHiddenKeyWrapper.updateTuple failed (Changing device number and hosting information at the same time is not allowed.) for DEI id (261)
Module Main
File Name and Line Number ESM_DEI_Storage_Adaptor.cpp;15352
-
try to untick the secondary element in user and device , then delete the device
-
When going to User and Services Configuration the Secondary Element is grayed out and I cannot change it.
-
to be sure : are you in the primary ESM ?
-
Yes, I have confirmed that I am in the primary ESM.
-
In the maintenance command try :
Gdm check.... Then : gdm repair
And try to delete after
-
I just tried and it didnt seem to fix anything. I think I might end up having the company that installed our system originally take a look and see if they can fix it. This one has been a real head scratcher.
Thanks for your help.
----------------------------------------------------------------------------
Checking for missing local hosted service ...
957 records processed in total.
0 Hosted User Service records require to be repaired.
0 Hosted System Service records require to be repaired.
Checking Hosted System Service for missing local directory number or unknown host ...
56 records processed in total.
0 Hosted System Service records are invalid.
0 duplicated Hosted System Service records are found.
Checking Hosted User Service for missing local directory number or unknown host or invalid service type ...
871 records processed in total.
0 Hosted User Service records are invalid.
0 Hosted User Service records have invalid service type.
4 duplicated Hosted User Service records are found.
Checking for missing user information in local Telephone Directory ...
831 records processed in total.
1 Telephone Directory records have invalid or are missing user information.
Checking local hosted user data missing associated Telephone Directory ...
774 records processed in total.
0 local hosted users missing associated Telephone Directory have been found.
0 local hosted User To Hosted User Service Map missing associated Telephone Directory have been found.
Checking invalid Hosted User Service Dependency records ...
0 records processed in total.
0 invalid Hosted User Service Dependency records have been found.
Command completed. Some data inconsistencies are detected.
Output saved at /db/gdm/GDMDataCheckResult.txt
Repairing for missing local hosted service ...
957 records processed in total.
0 Hosted User Service records require to be repaired.
0 Hosted System Service records require to be repaired.
Deleting Hosted System Service for missing local directory number or unknown host ...
56 records processed in total.
0 invalid Hosted System Service records have been deleted.
Deleting or updating Hosted User Service for missing local directory number or unknown host or invalid service type ...
871 records processed in total.
0 invalid Hosted User Service records have been deleted.
0 Hosted User Service records with invalid service type have been corrected.
Repairing for missing user information in local Telephone Directory ...
831 records processed in total.
0 Telephone Directory records with invalid or missing user information have been repaired.
Deleting local hosted user data missing associated Telephone Directory ...
774 records processed in total.
0 local hosted users missing associated Telephone Directory have been deleted.
0 local hosted User To Hosted User Service Map missing associated Telephone Directory have been deleted.
Deleting invalid Hosted User Service Dependency records ...
0 records processed in total.
0 invalid Hosted User Service Dependency records have been deleted.
GDM data repair completed.
-
The only way to fix this is by going in sdsdebug mode.
In maintenance command with auto complete disable
sdsdebug ON
The logout and login, you will see new sds form.
In the sds debug form
Users and Device then/Hosted Service
change and remove secondary element for the DN in problem. It may say internal errors, just click ok
type sdsdebug OFF to disable it.
Your problem will be fix.
-
The only way to fix this is by going in sdsdebug mode.
In maintenance command with auto complete disable
sdsdebug ON
The logout and login, you will see new sds form.
In the sds debug form
Users and Device then/Hosted Service
change and remove secondary element for the DN in problem. It may say internal errors, just click ok
type sdsdebug OFF to disable it.
Your problem will be fix.
Thanks for the steps. I wasnt really finding anything when I looked up sds debug mode. This is the solution.
-
I'd be very careful with SDS debug if I were you. This is a hidden menu and only Mitel tech support could look into it. Other experienced technicians are also fiddling with it but honestly, is not for everyone.
You can easily screw things up and would be harder to repair the DB.
There is no easy solution to your problem, even in SDS debug as every scenario is different. Doesn't work to follow certain steps, you would need to try different things in there.
You can try a DBMS check full but might end up with a DB corruption. A backup/restore might work but there is no guarantee.
Sent from my SM-N9005 using Tapatalk
-
I'd be very careful with SDS debug if I were you. This is a hidden menu and only Mitel tech support could look into it. Other experienced technicians are also fiddling with it but honestly, is not for everyone.
You can easily screw things up and would be harder to repair the DB.
There is no easy solution to your problem, even in SDS debug as every scenario is different. Doesn't work to follow certain steps, you would need to try different things in there.
You can try a DBMS check full but might end up with a DB corruption. A backup/restore might work but there is no guarantee.
Sent from my SM-N9005 using Tapatalk
A DBMS check will not cause DB corruption, it will only alert you to existing corruption.