"Create a Grants Rights Script" error in rs db configaration

Hi,

While I'm trying to configure rs db configuration, I’m getting "Create a Grants Rights Script" error when I click Apply button in rs configuration UI.

For this setup; I’m using 32-bit rs on 64-bit windows 2003 server and trying to connect 64-bit sql db instance on a different 64-bit box . both boxes are in same windows domain. I could also able to create rs db from rs configuration UI successfully. I'm using sql sa credentials and installed SQL SP1 on both boxes. Pl let me know how to fix this error.

Complate error message is,

System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String machine)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String dbServer)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String connectionString, String server, String database, ConfigurationCredentialsType credsType, String account, String password, Boolean upgrade, String dbVersion)

Thanks in advance

Ram

did you ever resolve this problem. I'm gettnig the same error.|||

Hi Greg,

I would suggest to start from here:

http://msdn2.microsoft.com/en-us/library/ms365170.aspx

http://msdn2.microsoft.com/en-us/library/ms159093.aspx

Mihaela

"Create a Grants Rights Script" error in rs db configaration

Hi,

While I'm trying to configure rs db configuration, I’m getting "Create a Grants Rights Script" error when I click Apply button in rs configuration UI.

For this setup; I’m using 32-bit rs on 64-bit windows 2003 server and trying to connect 64-bit sql db instance on a different 64-bit box . both boxes are in same windows domain. I could also able to create rs db from rs configuration UI successfully. I'm using sql sa credentials and installed SQL SP1 on both boxes. Pl let me know how to fix this error.

Complate error message is,

System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String machine)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String dbServer)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String connectionString, String server, String database, ConfigurationCredentialsType credsType, String account, String password, Boolean upgrade, String dbVersion)

Thanks in advance

Ram

did you ever resolve this problem. I'm gettnig the same error.|||

Hi Greg,

I would suggest to start from here:

http://msdn2.microsoft.com/en-us/library/ms365170.aspx

http://msdn2.microsoft.com/en-us/library/ms159093.aspx

Mihaela

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NFThis probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NFThis probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NFThis probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NF
This probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005