Ok, you click the obvious, the statement which says "Click for Assistance." You see a page with a variety of suggestions.
Great, now what?

The goal of this page is to walk you through the various causes for this problem and help you determine which one pertains to your code. Locating the root cause is the hard part, repairing is simple! Some of the instructions can be confusing so the following is a sort of checklist of known causes of the ID/U# Mismatch and what you can do about it.

  Is there anything there?
In other words, is there a User ID and U#? If not, your code is not complete. Somehow, the system left off the vital identifying parameters. Why/how this happened isn't nearly as important as the fact that the code needs replaced.
  Yes, this is me! What do I do?
Delete the code currently on your site, log in, go to View Websites, locate the URL, click "Get SSNB Code", and install. This code should be correct. View the site, reload/refresh if necessary. Be sure to allow several minutes for all computers to accept the communication.

  Is this the first membership of a new stack?
  Did you just add a new membership?
  Did you just split a larger stack?
Sometimes the system simply doesn't read new memberships or changes right away, as if the individual computers are giving each other the silent treatment. Compare the code you installed with that generated by the system. If the ID/U# are the same, the system isn't recognizing the information as it should.
  Yes, this is me! What do I do?
Re-save the membership for the one that should appear on that stack. View the site, reload/refresh if necessary It may take several minutes for the update to reflect. If there are multiple memberships assigned to a new U# (such as after a split), you may have to repeat the process for each, as the system is not recognizing the split. You might also need to reorder the old stack to remove them from it!

  Did the system change the U# assigned to this membership?
If you changed the URL for the membership(s) through the site management (edit) screen, the system would have changed the U# for the membership(s). This would render your code invalid. Sometimes just a system glitch will cause the U# to change. It's uncommon, but it happens. Compare the code you installed with that generated by the system and you'll likely see a difference, possibly even only one or two digits.
  Yes, this is me! What do I do?
Delete the current code, go to View Websites, locate the URL, click "Get SSNB Code", and install. This code should be correct. View the site, reload/refresh if necessary. Be sure to allow several minutes for all computers to accept the communication.

  Did you migrate from Yahoo!?
In October 2001, WebRing separated from Yahoo!, returning to an independent company. At this time, all members were asked to migrate back to WebRing (because it was the only way to transfer your personal information from Yahoo!). If you didn't migrate your membership(s) you need to do so.
  Yes, this is me! What do I do?
After you've migrated, you'll need to delete the code currently on your site, log in, go to View Websites, locate the URL, click "Get SSNB Code", and install. View the site, reload/refresh if necessary. Be sure to allow several minutes for all computers to accept the communication.

  Did you update the code?
Ok, so you did migrate, but did you update the code? Originally, it was thought you wouldn't have to, that Yahoo! would continue to support the old codes indefinitely. Once again, Yahoo!'s word wasn't worth a penny. They shut off the navbar servers early in 2002. A clue to this one is that the U# your code displays will be identical to what you see at http://z.webring.com/mbr?p=mu. The differences between this and a navbar that simply isn't recognized by the system is that you didn't recently install this code and your JavaScript will contain "yahoo" in it. Open your file as if you were going to edit, locate your WebRing navbar JavaScript and look for a command that says:

  Does the membership or ring still exist?
Perhaps the Ring or the membership no longer exists
  Yes, this is me! What do I do?
You can remove the coding from that page if you are not planning on submitting it to any more Rings. However, if you plan to resubmit, leave the code there. Double check that the code is still valid for that membership after submission. Also be prepared for the possibility of having to kick start the stack as shown above in the section "Did you just add a new membership?"

  What about "answer C - none of the above"?
Once in a while the perfect servers which provide this service fail to function. This will result in codes that work perfectly one day to display the mismatch another. This can be due to a server or power failure or other outside influences. These are situations over which you have no control. In these cases, there is little you can do. Once the source misfunction has been corrected, the stacks should begin to rebuild over the course of a few hours. You can usually help it along by re-saving the membership for the one that should appear on that stack. View the site, reload/refresh if necessary It may take several minutes for the update to reflect. If the source misfunction is not resolved, this will not work. These are generally discussed in the Help Forum (in the white box below).