SDS Distribution Error when creating embedded voicemail box (vMiVB 10.3)

[augiedawg6123]

Whenever I create an embedded voicemail box on MiVB, I get the following SDS Distribution Error:

11035

2025-Apr-30 15:22:25

vmicollab

modify

VM Mailboxes

com.mitel.sas.domain.service.EMEMInfo

And it contains all the information about the mailbox. I've got NuPoint integration enabled. Is this supposed to be happening? Wouldn't MiVB be smart enough not to try and push this to the MiCollab server?

Are SDS distribution errors just a thing with MiVB in general? I've gotten some alerts when I create hunt groups as well, and I just don't understand why these keep happening...

 

[Valamagules]

Check what you are sharing with other elements in the SDS sharing form. Not everything should be shared across the cluster, so make sure you only enable the things that should be shared. For example, the MiCollab would have nothing to do with Embedded VM, and because it does not understand this modification, it rejected it causing this SDS log.

Usually these SDS logs are rarely system impacting and can be ignored, but it’s important to note that it’s writing into a log file, the file can quickly fill up and cause further depletion of operational resources. I would either delete them or adjust the sharing form as I had eluded to earlier.

If the change is not making any negative operational impacts, you can safely ignore the SDS log.

 

[sokerwilliam]

What is the SDS?

 

[Billz66]

I think this is something new - we are also seeing it on the latest releases of micollab and MIVB
- i suspect that its trying to share something evmail related to micollab and micollab doesnt like it
knowing mitel, the developers have probably mucked up something and it will be a fix in next release

 

[jpruder]

SDS = System Data Synchronization, also any emem needs to have correct settings for sync from what I know

 

[augiedawg6123]

Check what you are sharing with other elements in the SDS sharing form. Not everything should be shared across the cluster, so make sure you only enable the things that should be shared. For example, the MiCollab would have nothing to do with Embedded VM, and because it does not understand this modification, it rejected it causing this SDS log.

Usually these SDS logs are rarely system impacting and can be ignored, but it’s important to note that it’s writing into a log file, the file can quickly fill up and cause further depletion of operational resources. I would either delete them or adjust the sharing form as I had eluded to earlier.

If the change is not making any negative operational impacts, you can safely ignore the SDS log.

Sorry for late reply, appreciate the info. I didn't even know you could choose what forms to share. "Voicemail Mailboxes" are already set to "none" on sharing.

 

[augiedawg6123]

I think this is something new - we are also seeing it on the latest releases of micollab and MIVB
- i suspect that its trying to share something evmail related to micollab and micollab doesnt like it
knowing mitel, the developers have probably mucked up something and it will be a fix in next release

Okay that makes me feel a little better. Kind of frustrating trying to learn a new platform and don't understand how things work in general vs. what is a software defect lol.

 

[AH64Armament]

Whenever I create an embedded voicemail box on MiVB, I get the following SDS Distribution Error:

11035

2025-Apr-30 15:22:25

vmicollab

modify

VM Mailboxes

com.mitel.sas.domain.service.EMEMInfo

And it contains all the information about the mailbox. I've got NuPoint integration enabled. Is this supposed to be happening? Wouldn't MiVB be smart enough not to try and push this to the MiCollab server?

Are SDS distribution errors just a thing with MiVB in general? I've gotten some alerts when I create hunt groups as well, and I just don't understand why these keep happening...

This is a known issue that should be resolved in 10.3 or later. I was told that it would be resolved in 10.2, but that didn't happen.

The site that I have with this issue currently uses the Embedded Voicemail on one of their controllers.
They do have a MiCollab server that some of their users use the MiCollab app on their workstations.

When they make any changes to a mailbox (EMEM), we get that same error you show.

I recently upgraded their MiCollab to version 10.x and that has stopped the SDS errors from the Embedded Voicemail... so hopefully if you upgrade your MiCollab, you'll have similar results.

Note that each site that I have upgraded to MiCollab 10.x has required that I restore the backup a 2nd time AFTER all the applications have been installed. One site that had an upgrade to 10.x and a subsequent upgrade to a newer 10.x had to also be restored a 2nd time during that upgrade as well... so there's something messed up on the scripts for 10.x upgrades.
You can't edit and save a user's info in the MiCollab.

 

[augiedawg6123]

This is a known issue that should be resolved in 10.3 or later. I was told that it would be resolved in 10.2, but that didn't happen.

The site that I have with this issue currently uses the Embedded Voicemail on one of their controllers.
They do have a MiCollab server that some of their users use the MiCollab app on their workstations.

When they make any changes to a mailbox (EMEM), we get that same error you show.

I recently upgraded their MiCollab to version 10.x and that has stopped the SDS errors from the Embedded Voicemail... so hopefully if you upgrade your MiCollab, you'll have similar results.

Note that each site that I have upgraded to MiCollab 10.x has required that I restore the backup a 2nd time AFTER all the applications have been installed. One site that had an upgrade to 10.x and a subsequent upgrade to a newer 10.x had to also be restored a 2nd time during that upgrade as well... so there's something messed up on the scripts for 10.x upgrades.
You can't edit and save a user's info in the MiCollab.

Thanks for the info, I'm not sure why I thought my MiVB server was on 10.3, turns out I'm on the following versions of MiVB/MiCollab in the lab:

MiCollab 10.0.0.26
MiVB 10.1.0.29

I'll have to upgrade and give it a try. Wish I could update the subject line of the post, didn't want to mislead people..

 

[AH64Armament]

Thanks for the info, I'm not sure why I thought my MiVB server was on 10.3, turns out I'm on the following versions of MiVB/MiCollab in the lab:

MiCollab 10.0.0.26
MiVB 10.1.0.29

I'll have to upgrade and give it a try. Wish I could update the subject line of the post, didn't want to mislead people..

That's understandable.

I don't think the issue has been corrected in MiVB 10.3... but in MiCollab 10.x

The issue seems to have been introduced in MiVB 10.0 or 10.1