Provision Eroor

Hello All
Error while provisioning
Windows Rights Management Services could not be provisioned on this server.

An error occurred during the provisioning process. Any changes made during 
the provisioning process have been rolled back. See Windows Rights Management 
Services Help for more information about the provisioning process.

Failed to enroll the server. If you requesting a new certificate for a root 
certification server, verify that you can connect to the internet and that 
you have set your proxy settings if they are required, and then try again. If 
you are requesting a new certificate for a licensing server, verify that you 
can connect to the root certification server, and then try again

Details 

at 
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Enroll(Boolean
fEnrollOffline) 
      at 
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Run() 
      at 
Microsoft.DigitalRightsManagement.Configuration.UI.ProvisionCommon.Page_Load(Obj
ect sender, EventArgs e)

InnerException

The underlying connection was closed: Unable to connect to the remote server.

      at 
Microsoft.DigitalRightsManagement.Configuration.UddiServiceFinder.FindService(St
ring tmodel, String proxy) 
      at 
Microsoft.DigitalRightsManagement.Configuration.ServiceFinder.GetCloudEnrollment
ServiceURL(String proxy) 
      at 
Microsoft.DigitalRightsManagement.Configuration.EnterpriseEnrollment.MakeEnrollR
equest(EnrollParameters ep) 
      at 
Microsoft.DigitalRightsManagement.Configuration.EnterpriseEnrollment.Enroll(Bool
ean fEnrollOffline) 
      at 
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Enroll(Boolean
fEnrollOffline)

hi,

Please verify the following step by step:

The most common provisioning issue occurs when RMS was previously installed 
in an Active Directory forest, but the previous SCP is not removed prior to 
reprovisioning. Remove the SCP by using Active Directory Sites and Services 
or the RMS Administration Web site. Select the Show Services node, and then 
delete the RightsManagementServices node.

The errors provided during provisioning are typically quite useful in 
determining the cause of the problem at hand.

also ensure that you dont run into:

# Insufficient user rights: Look at the rights of the .asmx files in IIS, 
and then make sure that you have the appropriate rights to execute the 
proper files. Turn on auditing to help diagnose this.

# SQL Server not running: On a fresh install, Microsoft SQL Server.does not 
automatically start. Be sure that it is running before attempting to 
provision. Also, double-check that the current user has appropriate
rights to perform the SQL Server operations required, such as adding a 
database and modifying the schema.

If the enterprise RMS server does not have Internet access, provisioning can 
be completed by using the Offline option. This entails saving the enrollment 
request to a file and then copying that file to a machine that has Internet 
access. From there, you can complete the enrollment process, save the SLC to 
a file, copy that file back to your RMS server, and then import the SLC. 
Proxy settings should also be checked.some proxy configurations require 
authentication, but the authentication may be transparent to the end users. 
If networks are slow, a timeout may occur during provisioning. The default 
time allowed is 5 minutes (300 seconds), but this can be increased by 
modifying the:

<httpRuntime executionTimeout="300" /> setting in the web.config
file 
located in the C:\Windows\RMS\Provision\ directory.

HTH
"Asif" <Asif@discussions.microsoft.com> wrote in message 
news:5133F00C-312D-484C-8960-7182A1E38A87@microsoft.com...
> Hello All
> Error while provisioning
> Windows Rights Management Services could not be provisioned on this 
> server.
>
> An error occurred during the provisioning process. Any changes made during
> the provisioning process have been rolled back. See Windows Rights 
> Management
> Services Help for more information about the provisioning process.
>
> Failed to enroll the server. If you requesting a new certificate for a 
> root
> certification server, verify that you can connect to the internet and that
> you have set your proxy settings if they are required, and then try again.

> If
> you are requesting a new certificate for a licensing server, verify that 
> you
> can connect to the root certification server, and then try again
>
> Details
>
> at
>
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Enroll(Boolean

> fEnrollOffline)
>      at
> Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Run()
>      at
>
Microsoft.DigitalRightsManagement.Configuration.UI.ProvisionCommon.Page_Load(Obj
ect 
> sender, EventArgs e)
>
> InnerException
>
> The underlying connection was closed: Unable to connect to the remote 
> server.
>
>      at
>
Microsoft.DigitalRightsManagement.Configuration.UddiServiceFinder.FindService(St
ring 
> tmodel, String proxy)
>      at
>
Microsoft.DigitalRightsManagement.Configuration.ServiceFinder.GetCloudEnrollment
ServiceURL(String 
> proxy)
>      at
>
Microsoft.DigitalRightsManagement.Configuration.EnterpriseEnrollment.MakeEnrollR
equest(EnrollParameters 
> ep)
>      at
>
Microsoft.DigitalRightsManagement.Configuration.EnterpriseEnrollment.Enroll(Bool
ean 
> fEnrollOffline)
>      at
>
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Enroll(Boolean

> fEnrollOffline)
>
> 

Dear Faisal Hussain

Thankyou for your useful support, I followed your instructions and problem 
is now solved.
Thankyou and God Bless you.

Asif

"Faisal Hussain" wrote:

> hi,
> 
> Please verify the following step by step:
> 
> The most common provisioning issue occurs when RMS was previously installed

> in an Active Directory forest, but the previous SCP is not removed prior to

> reprovisioning. Remove the SCP by using Active Directory Sites and Services

> or the RMS Administration Web site. Select the Show Services node, and then

> delete the RightsManagementServices node.
> 
> The errors provided during provisioning are typically quite useful in 
> determining the cause of the problem at hand.
> 
> also ensure that you dont run into:
> 
> # Insufficient user rights: Look at the rights of the .asmx files in IIS, 
> and then make sure that you have the appropriate rights to execute the 
> proper files. Turn on auditing to help diagnose this.
> 
> # SQL Server not running: On a fresh install, Microsoft SQL Server.does not

> automatically start. Be sure that it is running before attempting to 
> provision. Also, double-check that the current user has appropriate
> rights to perform the SQL Server operations required, such as adding a 
> database and modifying the schema.
> 
> If the enterprise RMS server does not have Internet access, provisioning
can 
> be completed by using the Offline option. This entails saving the
enrollment 
> request to a file and then copying that file to a machine that has Internet

> access. From there, you can complete the enrollment process, save the SLC
to 
> a file, copy that file back to your RMS server, and then import the SLC. 
> Proxy settings should also be checked.some proxy configurations require 
> authentication, but the authentication may be transparent to the end users.

> If networks are slow, a timeout may occur during provisioning. The default

> time allowed is 5 minutes (300 seconds), but this can be increased by 
> modifying the:
> 
> <httpRuntime executionTimeout="300" /> setting in the
web.config file 
> located in the C:\Windows\RMS\Provision\ directory.
> 
> HTH
> "Asif" <Asif@discussions.microsoft.com> wrote in message 
> news:5133F00C-312D-484C-8960-7182A1E38A87@microsoft.com...
> > Hello All
> > Error while provisioning
> > Windows Rights Management Services could not be provisioned on this 
> > server.
> >
> > An error occurred during the provisioning process. Any changes made
during
> > the provisioning process have been rolled back. See Windows Rights 
> > Management
> > Services Help for more information about the provisioning process.
> >
> > Failed to enroll the server. If you requesting a new certificate for a

> > root
> > certification server, verify that you can connect to the internet and
that
> > you have set your proxy settings if they are required, and then try
again. 
> > If
> > you are requesting a new certificate for a licensing server, verify
that 
> > you
> > can connect to the root certification server, and then try again
> >
> > Details
> >
> > at
> >
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Enroll(Boolean

> > fEnrollOffline)
> >      at
> >
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Run()
> >      at
> >
Microsoft.DigitalRightsManagement.Configuration.UI.ProvisionCommon.Page_Load(Obj
ect 
> > sender, EventArgs e)
> >
> > InnerException
> >
> > The underlying connection was closed: Unable to connect to the remote

> > server.
> >
> >      at
> >
Microsoft.DigitalRightsManagement.Configuration.UddiServiceFinder.FindService(St
ring 
> > tmodel, String proxy)
> >      at
> >
Microsoft.DigitalRightsManagement.Configuration.ServiceFinder.GetCloudEnrollment
ServiceURL(String 
> > proxy)
> >      at
> >
Microsoft.DigitalRightsManagement.Configuration.EnterpriseEnrollment.MakeEnrollR
equest(EnrollParameters 
> > ep)
> >      at
> >
Microsoft.DigitalRightsManagement.Configuration.EnterpriseEnrollment.Enroll(Bool
ean 
> > fEnrollOffline)
> >      at
> >
Microsoft.DigitalRightsManagement.Configuration.ProvisioningBase.Enroll(Boolean

> > fEnrollOffline)
> >
> >