If the provider information is correct and the provider is up, the provider's test page is displayed.
If the URL is correct and the provider is up, there may be a problem with the configuration of the portal repository.
Ensure that the width value is an integer value (preferably between 1 and 100).
If the WSDL URL has not changed, there could be some data inconsistency.Verify that the URL specified for the producer registration is correct and that the producer is up and running.If the problem persists, then request the portal administrator to delete the existing local user profile using the wwsec_api.delete_portal_user API. Ensure that the user is already a member of the group when it is assigned as the default group.Report the error to your portal administrator and request that the appropriate privileges be granted if needed.To edit an existing schema for this purpose, select Edit Schema in the Schema portlet.
Check whether the Oracle Internet Directory port is operational and that the Oracle Portal configuration is referring to the correct host name and port.After being managed by the browser, the cookies were sent to any other Web server that: Check whether the provider has a registration port.If a registation port exists, contact the provider administrator and request that the provider supply the necessary registration handle.One way to verify this is to enter the registration URL in a browser.If the URL is correct and the producer is up and running, you will see the producer's WSDL document.If necessary, contact the portal administrator to confirm the minimum number of numeric characters required for passwords.