Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
  Results
CMS-XML Launching SBM System Administrator or SBM Login Screen give error "InitExtension Failed" "License Server XXXX could not be contacted"
Launching SBM System Administrator or SBM Login Screen give error "InitExtension Failed" "License Server XXXX could not be contacted "
CMS-XML Composer can not deploy when one environment is down
In certain circumstances an attempt to deploy to a working environment will fail, the message indicating the the "authentication server could not be contacted " on a different environment, that is currently unavailable. This can happen when the last deploy by this user of any ProcessApp was to an environment that is now unavailable, even when you are trying to deploy elsewhere. If you know the environment will be restored to activity soon, then Publish from Composer and Deploy from Application Repository.
CMS-XML SBM: Users get error "InitExtension Failed" and "License server could not be contacted"
SBM: Users get error "InitExtension Failed" and "License server could not be contacted "
CMS-XML Error "InitExtension Failed" when accessing SBM (TeamTrack or Business Mashups)
the folder. License Server Could Not Be Contacted

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs