Since CloudPortal Services Manager v10 was released last December, the support forum has been a key resource for CSPs to obtain installation problems resolved. In this post, I will highlight the solutions to the most frequently raised problems in the forum, hope to give some context to help others get issues resolved quickly.
Creation of the first location
Creation of the first location was the trickiest part of the deployment process. Here are some common questions in this area and how to go about solving them.
Log fails on behalf of the CSP administrator
After completing all deployment steps, you try to connect with the CSP administrator and receive the error "Your information ID is not valid. Please try again or contact your service provider. "
Background
frontal authentication is provided by the Directory Web service. If this service is not working, or are not accessible (for example, because of the rules of firewall), you will see the login failures in the web.
provisioning requests are recorded in the OLM database and sent to the provisioning engine to Processing. The configuration tool successfully returns if supply applications are able to be saved and sent to the OLM Provisioning Engine. However, supply applications may not be processed if the Cortex Queue Monitor service is not running or an error occurs with one of the requests.
Resolution
Make sure that the Web Directory service is running and is accessible. View topic Web Directory Issues related Service below for details. If these checks pass, then verify that the administrator account exists in Active Directory. If it does not, then the provisioning requests to create the first location, the client and the user were either untreated, or not successfully executed
To see if supply requests been treated or not.
- Log on to the Provisioning Engine server and verify that the "Cortex Queue Monitor service" is running.
- Open Provisioning Manager from the Start menu, drill down to message queues> My computer> private tails , and check the queues and "cortexrequest" "cortexbulkrequest" for all unprocessed messages.
- If any of the above steps reveals a problem, stop the Cortex Queue Monitor service (CortexQueueMonitor.exe the process may take a minute or two to effectively end) and start again
to see if any errors occurred supply .:
- log on to the OLM database and "SELECT * fROM RequestLog WHERE gravity = 2 "
to enable tracing in the queue Monitor.
- Log on to the Provisioning Engine server and open "% ProgramFiles (x86)% Citrix Cortex Provisioning Engine CortexQueueMonitor.exe.config" in a text editor.
- Find the item "
" and change the value attribute to "All". - Find the item "
" and uncomment. Note the log file specified in the initializeData attribute and set accordingly if necessary. - Save the configuration file and restart the queue monitor waits as described above.
an error related to Web Directory service was returned
in the primary location assistant, an error occurs one of the following steps:
- Web services directory register Location
- domain Controllers register
Or an error in the Web directory service log file references.
Background
in the main location assistant, a number of operations on the directory Web service is invoked to provide the OU structure and user, as well as to list the servers in the environment. If the service is not running and accessible, which may cause the assistant principal at the failure location
Resolution
Make sure that the Web Directory service is running: .
- Log on to the server where the Web service is installed Directory
- at the boot prompt, run "inetmgr" drill down on the site "CortexServices "and find the application" Directory ".
- -click right and select "Switch to Content View."
- Right click "Directory.asmx" and select "Browse." This should launch the service operations available in IE.
If you receive an HTTP 503 "Service Unavailable" error or an HTTP 401 error "unauthorized" in step 4, the most common reason is that the credentials for the identity of the application pool is incorrect. To solve this: ..
- Find the DirectoryWSAppPool in IIS and rate user account it uses
- Reset this user password in AD
- Run the setup wizard for Web directory service again, passing in the new user password.
If you receive an error mentioning restrictions ISAPI / CGI, it is possible that the ASP.NET ISAPI filters are not enabled v4. Try the following:
- In a command prompt, run " Windows Microsoft.NET Framework64 v4.0.30319 aspnet_regiis.exe -ir -enable"
Make sure the Directory Web service can be accessed from the server on which the Web server role is installed, and from the server on which you run the wizard primary location. Check for firewall rules that block the required ports. A summary of firewall requirements can be found here on eDocs: http://support.citrix.com/proddocs/topic/ccp-10/ccp-10-system-requirements-roles.html[1945002~~number=plural]
overcoming a primary location error provisioning
documentation recommends backing of CPSM databases before configuring the first location so that if an error occurs, you can fix the problem (eg, using advice highlighted above), return to an instant cleaning databases, and executing the first location wizard again. No database backups official recommendation is to reinstall from scratch. However, it may be possible to recover the establishment before resorting to drastic measures. Here are two ways to do this.
Set the database
The first approach is to try to manually bring the base back data in a state that allows the first location and customers to provision again. To do this, you must delete the records of the customer and the location specified above by executing the following SQL commands:
USE OLM EXECUTE sp_CustomersDelete @CustomerID = 1 DBCC CHECKIDENT ( "clients" RESEED, 0) DBCC CHECKIDENT ( "users" RESEED, 0) = 1 EXECUTE sp_LocationsDelete @LocationID DBCC CHECKIDENT ( 'lOCATIONS' RESEED, 0)
locations are given ID from 1. If you ran the first assistant location multiple times, there may be more location in the database to be cleaned. "SELECT * FROM locations" to verify this.
Redeploy the database
Another approach is to redeploy the system databases, manually update the deployment configuration file, and rerun all configuration assistants .
- Redeploy the database
- If you use the same SQL Server instance, delete the databases (OLM, OLMReports & ExchangeLogs) and connections (OLMUser, OLMReportsUser, CortexProp & ExchangeLogsUser) created by the configuration tool
- Rerun the wizard system Databases. Specify a different path for the deployment configuration file so that the original is not overwritten.
- Create backups of the new databases
- Update the original configuration file deployment
- Replace all property in the original configuration file the values set in the newly created one.
- reconfigure all server roles
- For each server role (Web Directory, Provisioning Engine, Web), run the configuration wizard again, said the original configuration file was edited by hand earlier.
- Run the first assistant to the location again
Hope this helps you go with deployments CPSM faster.
0 Komentar