Random Login/Passwords not working with iMIS Membership Web Service

We have a client who upgraded from 10.6 to 15.1.1 back in September. They also went from using the e-Series login to the iMIS Membership Web Services on their website. The problem they are encountering is that random member login/passwords are not working, nor will the Password reset work for those users. This isn't happening for all members however. If a staff member changes a member's password within iMIS, they then are able to login on the website via the web service with no problem. We have verified that all IDs exist in Name_Security, Name_Security_Groups, & Name_Fin.

The Event Viewer on the App Server is returning "Membership credential verification failed." for those users who can't login.

Anyone else encountering this? Is there a solution? 


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

We're also having this

We're also having this issue, we will set their password on a back office IMIS and when they try to login an error message: "User Unknown Error Provider". Any idea what could it be?..

Thank you,

Net Contacts are out of Sync

I have just resolved this issue for our clients and the issue is the NetContacts are not in sync, There is a method. Let me know I can explain the proceses.

Net Contacts are out of Sync.

How did you resolved the issue? Can you please explain the process and what do I need to update? You can send me an email at TBalacano@yogaalliance.org I would greatly appreciate your help.

Thank you,

I would be interested in

I would be interested in learning how to resolve this as well. At your convenience, please let me know how at khudson@wmc.org.

Thank you,


We are experiencing this

We are experiencing this issue as well. Can you tell me what the process is? szhang@cmaontario.org
I tried resyn net contacts and that didn't fix it for us.


Same problem

Hi guys,

We are having the same problem.  Some users can't login, and when they try to reset their password they get "Error: Login Error".  This creates an event in the app server saying "Membership credential verification failed".  We created the users in 10.6 using the eSeries tool, then upgraded to 15.1.3.

We've put through an SMR to ASI but if you have been able to fix this can you post the solution here for future reference?

Thanks guys,


Sync NetContacts

We were able to resolve this by running the "Sync NetContacts" option the DBRepair utility.


Enable triggers first

Running the Synchronize NetContacts appears to help. But we had cases where this process would run endlessly - because two triggers on the Name table somehow got disabled. Check to see if any triggers are disabled:


SELECT name, is_disabled FROM sys.triggers

In our case, these two were showing up as disabled:


To re-enable them:

ALTER TABLE [Name] ENABLE TRIGGER asi_Name_Insert_Update;

Then run Synchronize NetContacts.

Another thing to try, which sometimes works for us, is to delete the customer's record in Name_Security_Groups. Also, watch out for any customers that have 2 records in that table:

select ID
from dbo.Name_Security_Groups
having count(*) > 1

I don't know why any of this helps.


Triggers and Security Groups

I'm now experiencing this. I ran your Name_Security_Groups select statement and found that I have short list of ID's (one of which I know I am having problems with when I try to create an account for), would you be willing to share how to delete them?

Triggers and Security Groups

I don't know if this is the best approach, but without any guidance from ASI, I stumbled across a solution that appears to work for us.

When we get duplicate Name_Security_Groups records, one of them will have a security group of 'Anonymous', and the other is blank. Deleting the one with a blank security group clears the issue for us most of the time:

delete from dbo.Name_Security_Groups
where id in ('10326') 
and len(security_group) = 0

Thanks so much for this! 

Thanks so much for this!  Of course I'll do this against our test database first then take appropriate action before running on live. 

Sarah LeCouffe