Installing the Reporting Services Client Print ActiveX Control - Revision history

Robert at 03:59, 8 August 2011

2011-08-08T03:59:51Z

← Older revision		Revision as of 03:59, 8 August 2011
Line 1:		Line 1:
	Created: 14 October 2009. Last Reviewed: ~~14 October 2009~~		Created: 14 October 2009. Last Reviewed: 08 August 2011


	EEE Reports are delivered using Microsoft SQL Server Reporting Services, a component of SQL Server 2005 and SQL Server 2008. Reporting Services displays reports to users in a web browser. In order to print reporting services reports to a client-connected printer, Reporting Services uses a small ActiveX component known as RSClientPrint. Upon first attempt to use the client print function (or first attempt after installing a Reporting Services update such as an SQL Server service pack), IE will prompt the user to download and install the ActiveX control.		EEE Reports are delivered using Microsoft SQL Server Reporting Services, a component of SQL Server 2005 and SQL Server 2008. Reporting Services displays reports to users in a web browser. In order to print reporting services reports to a client-connected printer, Reporting Services uses a small ActiveX component known as RSClientPrint. Upon first attempt to use the client print function (or first attempt after installing a Reporting Services update such as an SQL Server service pack), IE will prompt the user to download and install the ActiveX control.

Robert: /* To Manually Install the ActiveX Control: */

2011-08-08T03:59:33Z

To Manually Install the ActiveX Control:

← Older revision		Revision as of 03:59, 8 August 2011
Line 14:		Line 14:

	The cab file contains the following which should be copied to the '''c:\windows\Downloaded Program Files folder''' on the client machine:		The cab file contains the following which should be copied to the '''c:\windows\Downloaded Program Files folder''' on the client machine:

			NOTE: Default Windows system permissions may mask the files in this directory. Copying the files into the folder via a command line should make it clear that the files have actually been copied.

	* gdiplus.dll		* gdiplus.dll

Robert at 03:57, 8 August 2011

2011-08-08T03:57:20Z

← Older revision		Revision as of 03:57, 8 August 2011
Line 61:		Line 61:
	</pre>		</pre>

	Note: This batch file uses psexec.exe from [http://technet.microsoft.com/en-us/sysinternals/~~bb545027.aspx~~ Sys Internals] to invoke commands (cmd.exe and regsvr32.exe) under a different (administrator) account. The Windows internal runas command cannot be used because runas does not accept passwords from the command line.		Note: This batch file uses psexec.exe from [http://technet.microsoft.com/en-us/sysinternals/bb897553 Sys Internals] to invoke commands (cmd.exe and regsvr32.exe) under a different (administrator) account. The Windows internal runas command cannot be used because runas does not accept passwords from the command line.

	Note that upon first execution of psexec.exe an EULA may be displayed to the user in a modal dialog box. To prevent this (which would stop a batch file from running in unattended mode), the command line switch /accepteula is used in the first call to psexec.exe.		Note that upon first execution of psexec.exe an EULA may be displayed to the user in a modal dialog box. To prevent this (which would stop a batch file from running in unattended mode), the command line switch /accepteula is used in the first call to psexec.exe.
Line 69:		Line 69:
	[[Reporting_Services_Client_Print_Control_cannot_load\|Reporting Services Client Print Control cannot load]]		[[Reporting_Services_Client_Print_Control_cannot_load\|Reporting Services Client Print Control cannot load]]

	[http://technet.microsoft.com/en-us/sysinternals/~~bb545027.aspx~~ Sys Internals PSExec.exe]		[http://technet.microsoft.com/en-us/sysinternals/bb897553 Sys Internals PSExec.exe]

Robert: /* See Also: */

2011-08-08T03:56:32Z

Robert at 03:55, 8 August 2011

2011-08-08T03:55:54Z

← Older revision		Revision as of 03:55, 8 August 2011
Line 8:		Line 8:
	# To save users having to accept the ActiveX installation prompts; or		# To save users having to accept the ActiveX installation prompts; or
	# If Internet Explorer security settings are such that the installation of the ActiveX control would not be permitted.		# If Internet Explorer security settings are such that the installation of the ActiveX control would not be permitted.
			# The installation via the 'yellow bar' prompt in Internet Explorer has failed on a previous occasion.

	===== To Manually Install the ActiveX Control: =====		===== To Manually Install the ActiveX Control: =====
	The ActiveX control files are in RSClientPrint.cab on the SQL Server in the Reporting Services bin directory. This is typically located in '''c:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin'''. Note that the MSSQL.4 directory is variable depending what SQL Server components are installed – Reporting Services may be in MSSQL.2 or MSSQL.3 etc.		The ActiveX control files are in RSClientPrint.cab on the SQL Server in the Reporting Services bin directory. This is typically located in '''c:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin'''. Note that the MSSQL.4 directory is variable depending what SQL Server components are installed – Reporting Services may be in MSSQL.2 or MSSQL.3 etc. SQL Server 2008 and above use MSRS* as the folder name for Reporting Services.


	~~The cab file contains~~ the ~~following which should be installed in c:\windows\Downloaded Program Files:~~

			The cab file contains the following which should be copied to the '''c:\windows\Downloaded Program Files folder''' on the client machine:

	* gdiplus.dll		* gdiplus.dll
Line 30:		Line 29:
	* RSClientPrint_1053.rll		* RSClientPrint_1053.rll
	* RSClientPrint_2052.rll		* RSClientPrint_2052.rll
	* RSClientPrint_3082.rll~~<br/>~~		* RSClientPrint_3082.rll


	Once thse files have been installed, RSClientPrint.dll needs to be registered:'''regsvr32.exe RFClientPrint.dll.'''If writing a batch file to automate this process it may be necessary to force the installation and registration of files above to run under a separate account with administrative privileges. The following batch file may be used as a guide:

			Once thse files have been installed, RSClientPrint.dll needs to be registered: '''regsvr32.exe "C:\Windows\Downloaded Program Files\RSClientPrint.dll"'''

	~~''@echo off''~~		If writing a batch file to automate this process it may be necessary to force the installation and registration of files above to run under a separate account with administrative privileges. The following batch file may be used as a guide:

	''@~~Rem Skip if already installed (might not work if attempting to upgrade an older version!)''~~		<pre>
			@echo off

	''if ~~exist "c:\Windows\Downloaded Program Files\gdiplus.dll" goto endd''~~		@Rem Skip if already installed (might not work if attempting to upgrade an older version!)

			if exist "c:\Windows\Downloaded Program Files\gdiplus.dll" goto endd

	~~''@Rem Specify source directory (copy of files from cab file)''~~

	~~''set srcpath=\\eee-server\~~files''		@Rem Specify source directory (copy of files from cab file)

			set srcpath=\\eee-server\files

	~~''@Rem Install Files''~~

	~~''%srcpath%\psexec.exe /accepteula -u administrator -p my-password cmd.exe /c xcopy %srcpath%\rsclient\* "c:\Windows\Downloaded Program~~ Files~~" /y''~~		@Rem Install Files

			%srcpath%\psexec.exe /accepteula -u administrator -p my-password cmd.exe /c xcopy %srcpath%\rsclient\* "c:\Windows\Downloaded Program Files" /y

	~~''@Rem Register DLL''~~

	~~''%srcpath%\psexec.exe -u administrator -p my-password regsvr32 "c:\Windows\Downloaded Program Files\RSClientPrint.dll" /s''~~		@Rem Register DLL

			%srcpath%\psexec.exe -u administrator -p my-password regsvr32 "c:\Windows\Downloaded Program Files\RSClientPrint.dll" /s

	~~'':endd''~~

			:endd
			</pre>

	Note: This batch file uses psexec.exe from ~~Sys Internals (~~[http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx ~~http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx][http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx)/ )~~] to invoke commands (cmd.exe and regsvr32.exe) under a different (administrator) account. The Windows internal runas command cannot be used because runas does not accept passwords from the command line.		Note: This batch file uses psexec.exe from [http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx Sys Internals] to invoke commands (cmd.exe and regsvr32.exe) under a different (administrator) account. The Windows internal runas command cannot be used because runas does not accept passwords from the command line.

			Note that upon first execution of psexec.exe an EULA may be displayed to the user in a modal dialog box. To prevent this (which would stop a batch file from running in unattended mode), the command line switch /accepteula is used in the first call to psexec.exe.
	Note that upon first execution of psexec.exe a EULA may be displayed to the user in a modal dialog box. To prevent this (which would stop a batch file from running in unattended mode), the command line switch /accepteula is used in the first call to psexec.exe.

	== See Also: ==		== See Also: ==
	If the Print Control fails to load, you may require updates to SQL Server:		If the Print Control fails to load, you may require updates to SQL Server:
	http://~~theoracle~~.~~magentaretail~~.com~~.au~~/~~wiki~~/~~index~~.~~php/Reporting_Services_Client_Print_Control_cannot_load~~		[Reporting_Services_Client_Print_Control_cannot_load\|Reporting Services Client Print Control cannot load]

			[http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx Sys Internals PSExec.exe]

Robert at 23:48, 15 March 2010

2010-03-15T23:48:57Z

← Older revision		Revision as of 23:48, 15 March 2010
Line 66:		Line 66:
	Note that upon first execution of psexec.exe a EULA may be displayed to the user in a modal dialog box. To prevent this (which would stop a batch file from running in unattended mode), the command line switch /accepteula is used in the first call to psexec.exe.		Note that upon first execution of psexec.exe a EULA may be displayed to the user in a modal dialog box. To prevent this (which would stop a batch file from running in unattended mode), the command line switch /accepteula is used in the first call to psexec.exe.

	= See Also: =		== See Also: ==
	If the Print Control fails to load, you may require updates to SQL Server:		If the Print Control fails to load, you may require updates to SQL Server:
	http://theoracle.magentaretail.com.au/wiki/index.php/Reporting_Services_Client_Print_Control_cannot_load		http://theoracle.magentaretail.com.au/wiki/index.php/Reporting_Services_Client_Print_Control_cannot_load

Robert at 23:48, 15 March 2010

2010-03-15T23:48:09Z

← Older revision		Revision as of 23:48, 15 March 2010
Line 67:		Line 67:

	= See Also: =		= See Also: =
			If the Print Control fails to load, you may require updates to SQL Server:
			http://theoracle.magentaretail.com.au/wiki/index.php/Reporting_Services_Client_Print_Control_cannot_load

Bevan at 04:16, 14 October 2009

2009-10-14T04:16:59Z

← Older revision		Revision as of 04:16, 14 October 2009
Line 13:		Line 13:


	The cab file contains the following which should be installed in c:\windows\Downloaded Program Files:* gdiplus.dll		The cab file contains the following which should be installed in c:\windows\Downloaded Program Files:


			* gdiplus.dll
	* rsclientprint.dll		* rsclientprint.dll
	* RSClientPrint_1028.rll		* RSClientPrint_1028.rll

Bevan at 04:16, 14 October 2009

2009-10-14T04:16:26Z

← Older revision		Revision as of 04:16, 14 October 2009
Line 10:		Line 10:

	===== To Manually Install the ActiveX Control: =====		===== To Manually Install the ActiveX Control: =====
	The ActiveX control files are in RSClientPrint.cab on the SQL Server in the Reporting Services bin directory. This is typically located in '''c:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin'''. Note, that the MSSQL.4 directory is variable depending what SQL Server components are installed – Reporting Services may be in MSSQL.2 or MSSQL.3 etc.		The ActiveX control files are in RSClientPrint.cab on the SQL Server in the Reporting Services bin directory. This is typically located in '''c:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin'''. Note that the MSSQL.4 directory is variable depending what SQL Server components are installed – Reporting Services may be in MSSQL.2 or MSSQL.3 etc.


Line 30:		Line 30:


	Once thse files have been installed, RSClientPrint.dll needs to be registered:'''regsvr32.exe RFClientPrint.dll'''If writing a batch file to automate this process it may be necessary ~~for~~ force ~~steps 2~~ and 3 above to run under a separate account with administrative privileges. The following batch file may be used as a guide:		Once thse files have been installed, RSClientPrint.dll needs to be registered:'''regsvr32.exe RFClientPrint.dll.'''If writing a batch file to automate this process it may be necessary to force the installation and registration of files above to run under a separate account with administrative privileges. The following batch file may be used as a guide:


Line 38:		Line 38:

	''if exist "c:\Windows\Downloaded Program Files\gdiplus.dll" goto endd''		''if exist "c:\Windows\Downloaded Program Files\gdiplus.dll" goto endd''


	~~''@Rem Create directory if necessary''~~

	~~''if not exist "c:\Windows\Downloaded Program Files" mkdir "c:\Windows\Downloaded Program Files"''~~


Line 63:		Line 58:


	Note: This batch file uses psexec.exe from Sys Internals ([http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx][http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx)/ )] to invoke commands (cmd.exe and regsvr32.exe) under a different (administrator) account. The Windows internal runas command cannot be used because ~~you cannot pass the password on~~ the command line ~~to runas~~.		Note: This batch file uses psexec.exe from Sys Internals ([http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx][http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx)/ )] to invoke commands (cmd.exe and regsvr32.exe) under a different (administrator) account. The Windows internal runas command cannot be used because runas does not accept passwords from the command line.

Bevan at 04:12, 14 October 2009

2009-10-14T04:12:42Z

← Older revision		Revision as of 04:12, 14 October 2009
Line 10:		Line 10:

	===== To Manually Install the ActiveX Control: =====		===== To Manually Install the ActiveX Control: =====
	# The ActiveX control files are in RSClientPrint.cab on the SQL Server in the Reporting Services bin directory. This is typically located in '''c:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin'''. Note, that the MSSQL.4 directory is variable depending what SQL Server components are installed – Reporting Services may be in MSSQL.2 or MSSQL.3 etc.		The ActiveX control files are in RSClientPrint.cab on the SQL Server in the Reporting Services bin directory. This is typically located in '''c:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin'''. Note, that the MSSQL.4 directory is variable depending what SQL Server components are installed – Reporting Services may be in MSSQL.2 or MSSQL.3 etc.
	~~# The cab file contains the following which should be installed in c:\windows\Downloaded Program Files:~~

	* gdiplus.dll
			The cab file contains the following which should be installed in c:\windows\Downloaded Program Files:* gdiplus.dll
	* rsclientprint.dll		* rsclientprint.dll
	* RSClientPrint_1028.rll		* RSClientPrint_1028.rll
Line 27:		Line 27:
	* RSClientPrint_1053.rll		* RSClientPrint_1053.rll
	* RSClientPrint_2052.rll		* RSClientPrint_2052.rll
	* RSClientPrint_3082.rll		* RSClientPrint_3082.rll<br/>

	~~# Once thse files have been isntalled, RSClientPrint.dll needs to be registered:'''regsvr32.exe RFClientPrint.dll'''~~

	If writing a batch file to automate this process it may be necessary for force steps 2 and 3 above to run under a separate account with administrative privileges. The following batch file may be used as a guide:		Once thse files have been installed, RSClientPrint.dll needs to be registered:'''regsvr32.exe RFClientPrint.dll'''If writing a batch file to automate this process it may be necessary for force steps 2 and 3 above to run under a separate account with administrative privileges. The following batch file may be used as a guide:

← Older revision		Revision as of 03:56, 8 August 2011
Line 67:		Line 67:
	== See Also: ==		== See Also: ==
	If the Print Control fails to load, you may require updates to SQL Server:		If the Print Control fails to load, you may require updates to SQL Server:
	[Reporting_Services_Client_Print_Control_cannot_load\|Reporting Services Client Print Control cannot load]		[[Reporting_Services_Client_Print_Control_cannot_load\|Reporting Services Client Print Control cannot load]]

	[http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx Sys Internals PSExec.exe]		[http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx Sys Internals PSExec.exe]