Error occurred while changing subscrption properties

Question

0.00/5 (No votes)

See more:

Hi,

I made changes to one of the table in the publication and run the snapshot, at subscriber end i have tried to change into sql server authentication(which was Basic authentication while connecting to publication before)using subscription properties and given correct username and password but when i click on "OK" button, it will display below error message

Value is longer than 128 that it should not exceed.
Parameter name: value (Microsoft.sqlserver.rmo)

tried to revert back the changes also will display same error.

Could you please let me know how to solve this problem.

Thanks,

Vasanth

Posted 13-Apr-10 5:48am

vasumagadi

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

vasumagadi · Answer 1 · 2010-04-14T02:24:00

Hi,

I found the solution for the above error.

i was trying to enter "username" and "Password" without removing the existing value completely.

So, Before add/modify any username and password we have to remove existing login credentials completely.

In my case this solved the problem.

Thanks,

Vasanth