Logout

Alt-N Discussion Groups > Outlook Connector Discussion Groups > Outlook Connector Support > Mdaemon Connector Accounts - Overall number not decreasing when account deleted

 [F] Alt-N Discussion Groups  / Outlook Connector Discussion Groups  / Outlook Connector Support  /

Mdaemon Connector Accounts - Overall number not decreasing when account deleted

[Richard, Kevin]
Kevin Richard
Newbie
Newbie
Posts: 3
Kevin Richard - 09:17am, Sep 3 2019

MD 19.0.3 with MD Connector 6.0.2. When accounts that used MD Connector are deleted, the number of accounts that shows up under "Accounts" for MD Connector on main screen (under "statistics") does not decrease. The MD Accounts and Activesync accounts numbers decrease when an account is deleted. We have 16 users, and if I go into MD Connector accounts in settings, it shows 16 accounts. On the main screen it says 22 accounts. As we have up to 25 users, don't want it to refuse to let us set up new accounts with MD Connector when the number on the main screen hits 25. Wondering if this number is stored somewhere that could be changed manually.

  All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items

Kevin Richard - Sep 4, 2019 1:20 pm (#1 Total: 2)  

 

Photo of Author
Kevin Richard
Newbie
Newbie
Posts: 3
I found the answer as to where the file is - the info is stored in GroupWareUsers.dat stored in Mdaemon\app folder. Not sure why the deleted accounts had not been removed from this file, but I deleted them manually from the file. I presume this problem will continue when I delete accounts in the future though.

David C - Sep 6, 2019 4:21 pm (#2 Total: 2)  

 

Photo of Author
David C
Guru
Guru
Posts: 1422
Yes, the list of MDaemon accounts that have been granted MDaemon Connector rights are stored in file "/MDaemon/App/GroupWareUsers.dat".

I am unable to reproduce the issue you describe on any of my MDaemon test machines.

Steps I performed for testing:

1) In the MDaemon console, click on "Setup" ) "MDaemon Connector..."

2) In the "MDaemon Connector" dialog box that appears, in the hierarchical tree on the left I click on the branch "Accounts"

3) To add all of the accounts on my MDaemon test machines to the list of MDaemon Connector accounts, I clicked on the button "Allow all accounts to connect using MDaemon Connector". This populated the list with all of the accounts on my test machine.

4) I then clicked the "OK" button to close the dialog box. The number of MDaemon Connector accounts displayed in the MDaemon Connector matches the number of accounts in my MDaemon Connector account list.

5) In the MDaemon console, click on "Setup" ) "MDaemon Connector..."

6) In the "MDaemon Connector" dialog box that appears, in the hierarchical tree on the left I click on the branch "Accounts"

7) I selected one of the accounts in the account list then clicked on the button "Remote" to remove the account

I then clicked the "OK" button to close the dialog box. The number of MDaemon Connector accounts displayed in the MDaemon Connector is now one less and again matches the number of accounts in my MDaemon Connector account list.

Again, I am unable to reproduce the issue you describe on any of my MDaemon test machines.





Troubleshooting suggestions:

Do you have any user credentials in the "Windows Service" dialog box?

  • http://help.altn.com/mdaemon/en/index.html?service_settings.htm

    If so, please remove those credentials from MDaemon and restart the MDaemon service.

    After removing the user credentials from MDaemon and restarting the service, does the issue you describe still occur?

    Normally MDaemon is configured to run as a Windows service. I assume that is the case on your computer.

    If so, do you experience the same issue when running MDaemon as an application rather than as a service?

    Run MDaemon as an application by performing the following steps:

    1) Stop the MDaemon service using whatever means you normally use (One can launch "services.msc", locate the service "MDaemon" in the window that appears and stop it, or one can open a Windows command prompt and issue the command "net stop MDaemon", etc.)

    2) If running a copy of Windows 7 or earlier, one can verify that all MDaemon processes have stopped by opening Windows task manager, going to the "Processes" tab, enabling the option "Show processes from all users", then looking for the following MDaemon processes and stopping them if they are still running.

    3) If running a copy of Windows 8 or later, one can verify that all MDaemon processes have stopped by opening Windows task manager, clicking on the link "More Details" at the bottom left, then going to the "Details" tab, then looking for the following MDaemon processes and stopping them if they are still running:

  • MDLaunch.exe

  • MDaemon.exe

  • CFEngine.exe

  • MDSpamD.exe

  • WorldClient.exe

  • WCXMPPServer.exe

  • ClamD.exe

    4) After verifying that all the processes have stopped, navigate to the folder "/MDaemon/App/", right-click on the file "MDaemon.exe", and select "Run as Administrator" from the menu that appears. If you are running an older version of Windows (earlier than Windows Vista), then double-click on the file "MDaemon.exe" in the folder "/MDaemon/App/" to run it as an application.



    MDaemon is now running as an application. Attempt to add and remove an account from the list of MDaemon Connector accounts. Is the account successfully removed and the number of accounts displayed in the MDaemon console one less?

    If the issue you describe does not occur when running MDaemon as a



  •   All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items



     Content:

    Read New | Search

     Guest:

    Email to Admin



    You are visiting as a Guest user.