Unable to Create New User Accounts For Data Feeds
(I branched out this post being it's a different issue)
Are you getting any errors in the UI or the W3WP/Job logs?
Is this for the User Name field in the Feed Information section on the General tab?
After upgrading our environment to 5.5 SP1 P1, we’re unable to save Datafeeds (either imported / copied or new), using User Name= ‘Other’, and entering a new Username.
We are getting the following error message:
No worries Shaun
Check your General User Parameter under Manage Security Parameters and see if that changed. The error looks like a password is being set that goes against the parameter.
Nothing has changed with regards to the General parameter. I've checked with the environemnt that we have not upgraded also to confirm. They are the same.
Interestingly, I can proceed with the Save if I use a pre exisitng username.
Thanks David. I've opened a ticket. Just interested to see if anyone else has noticed this issue in the meantime.
I'll update this thread when we get to the bottom of it.
Thanks for your help.
Did you try making a small change to the security parameter and re-saving it? You could even revert back to whatever you changed just to recommit the security parameter in case its having issues? It might be worth a try.
To me, this error looks like you're trying to create a DF user that has a username too similar to the Services Account Password that you set in the ACP. Have you tried changing your Services Account Password altogeher, or checking this username against the current one to see if too many characters match between them (per your service parameter settings)?
Thanks for the suggestions guys.
I've attempted making a change in the Security Parameter, saving, then creating a new DF with a new username, no joy.
I've used a variety of different usernames, none have been successful. We keep do use a naming convention for the usernames (not similar at all to the Services Account username or password) - & I have varied from this naming convention also, still no joy.
I take it you aren't experiencing this same issue in v5 SP1 P1?