Sharepoint 2010 - Secure Store error on creation every time

Every time I try to "Create New Secure Store Target Application", I enter the ID, Display Name etc etc and when I click Next it gives me the same error:
"Error. Your session has expired. Restart this wizard to continue."

I have tried it many times and always the same error so I cannot create a Secure Store.
I have restarted the SERVICE but it makes no difference. I've created a new KEY but no difference.

Does anyone have a solution to get this working? Without this, I am unable to access any external data connections from within SharePoint as using methods other than the Secure Store do not work either.

Many thanks
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


I remember similar session expired errors when the Server name contains an underscore.

You may rename the server(s) name, remove trouble some Service Apps if there is any  and try creating Secure store again.

Hope it may help you.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
stack888Author Commented:
Hi ShareD, thanks for the reply.
The Server does contain an underscore. In fact our naming convention has always been to use underscores for Server names specifically because it usually doesn't create any problem with any other system or software. If thats the reason, this is a real Bug that Microsoft have in their product.
The Server is our only Sharepoint Server and in Production for the whole Company, so changing Server names would be very challenging.
I'll see if I can find any workaround if this is indeed the issue.
Many thanks!
stack888Author Commented:
after speaking to MS support, your suggestion that it was related to an underscore in the Server name was proved correct. We did find a workaround without having to change the Server name though by adding a DNS entry and another alternate name in Sharepoint so all is good now.
You are most welcome stack888.

It would be great if you could share the work around for future reference.
stack888Author Commented:
yes, it was just a case of creating another alternate name in sharepoint and the relevant DNS entry for this in active directory, then it would work. The Microsoft guy wasn't sure if it would work and had said if not, it would require a rebuild or reinstall, which was really not possible on a production server right now!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.