App license could not be verified

Question

0.00/5 (No votes)

See more:

SharePoint2013

Good day,

We have three SP Servers. Two are SP Foundation and one is SP Server, we bought multiple licenses for one app on all three servers. One of the servers was a test server and we wanted to shut it down. After turning off the server we got a error and couldn't start the app on the other two servers.

This is the error:

https://social.technet.microsoft.com/Forums/getfile/834653

the app domains were different on all three servers. Do anyone know how to solve this problem? Thanks in advance.

What I have tried:

We started again the test server but it didn't helped.

Posted 1-Apr-16 1:28am

Member 12430415

Updated 1-Apr-16 1:52am

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)

ZurdoDev · Accepted Answer · 2016-04-01T01:52:00

1. Verifyed is spelled wrong so that is weird.
2. This site is for coding questions and you have a technical support issue.
3. Since this deal with licenses you may very well have to go to Microsoft directly.
4. I suggest opening a support issue with Microsoft or in a Tech Support forum.