• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Title: PowerServer failed to start. Failed to verify the license

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Title: PowerServer failed to start. Failed to verify the license

  1. How-to
0
Votes
Undo
  1. Bryant Burnard
    Bryant Burnard
  2. PowerServer
  3. Wednesday, 26 October 2022 18:59 PM UTC

PB 2021 Build 1509, Oracle 19

Something has changed in my environment, and not sure what else to check. I manually checked each of the sites mentioned in the error message: 

 https://apips.appeon.com, https://apips.appeon.net, https://apipsoa.appeon.com, https://apipsoa.appeon.net, https://apips2.appeon.com, https://apips2.appeon.net

and they brought back a happy face emoji. Erased my repos directory, and still getting the above error. 

Thoughts on what I should explore?

Thanks

Bryant

Select Error: Transaction does not exist. Transact...
Could not load file or assembly 'OracleManagedData...
Responses (3)
Aubrey Lin @Appeon
Aubrey Lin @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 October 2022 09:32 AM UTC
  2. PowerServer
  3. # 1

Hi Bryant,
Please try the following solutions:
1. Provide the error details (after “Failed to verify the license”). A screenshot will be better.
You can also get the error from the PowerServer log: https://docs.appeon.com/ps2022/Log4net_logging.html 
2. Start up the application from the PowerServer Web API from SnapDevelop instead of IIS.
Check the information on the Console. It will introduce possible internet reasons there.
3. If it’s ok when starting from SnapDevelop. Then it may be caused by your local IIS account settings.
Refer to https://www.appeon.com/how-solve-error-failed-verify-license-failed-get-valid-response-powerserver-project 
4. Try to delete the C# solution and build and deploy to regenerate one.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 26 October 2022 19:23 PM UTC
  2. PowerServer
  3. # 2

Hi Bryant;

  If your network (AV, Firewall & Proxy) are allowing these URLS and Port 443, you should see ...

Regards ... Chris

Comment
Bryant Burnard
  1. Bryant Burnard
  2. Thursday, 27 October 2022 14:21 PM UTC
Ok, found out it is a security issue on our side, and I'll work with that team to resolve the issue. Thanks for all of your advice Chris and Armeen!



B
  1. Helpful 2
There are no comments made yet.
Bryant Burnard
Bryant Burnard Accepted Answer Pending Moderation
  1. Wednesday, 26 October 2022 19:28 PM UTC
  2. PowerServer
  3. # 3

Hi Chris, I get this:

Comment
Load more comments
Bryant Burnard
  1. Bryant Burnard
  2. Wednesday, 26 October 2022 20:07 PM UTC
Hi Chris,

Yes, have the Auto Import, I'll check on the other info.
  1. Helpful
Bryant Burnard
  1. Bryant Burnard
  2. Wednesday, 26 October 2022 21:52 PM UTC
Hi Chris,

the Web API URL is set as: http://localhost:443

on the run Options are set as:

App URL preview: https://localhost:443/pvr

HTTPS is selected, host: LocalHost and port is 443



Not sure where do set the Domain info though, clues please





  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 26 October 2022 23:11 PM UTC
That's your problem... Both the App & the Web API server are vying for the same port. Normally, the Web API server is listening on port 5099 (default).
  1. Helpful 1
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.