HELP!!! Printer Delivery Extension not Printing Landscape

Hello All,

I'm using SQL Server 2005 Reporting Services, and I'm trying to have subscriptions print. To try this, I built, installed, and configured the printer delivery extension sample provided by Microsoft.

Everything appeared to be working fine. That is, I can schedule a report to print automatically using the printer delivery extension. However, the problem is that the reports always print portrait.

We have a number of reports--some are portrait and some are landscape. So, obviously, I need the landscape reports to print lanscape.

I've even tried "hard-coding" the page width and page height parameters in the printer delivery extension to try to force it to print landscape, but it still always prints portrait.

Would any one know how to have reports that are delivered to a printer actually print in the way they are created (i.e., print landscape if the report is set up as a landscape report)?

Do I have to use the IMAGE format? Could I use PDF? If so, how?

Thanks!

Hi,

there is a likewise issue if you use linked reports in RS - the linked report does not contain the original page settings.

It probably could be that you would have to set the page settings programmatically like described by Brian Welcker for the linked reports:
http://www.fits-consulting.de/blog/PermaLink,guid,e3f1cf4a-f9d6-44d8-86e5-84a59531f87c.aspx

hth...

cheers,
Markus

|||

Thanks for the info. Markus. Unfortunately, setting the page settings programmatically didn't help. All reports and linked reports always print portrait, not landscape.

Therefore, would any one have any ideas on how to use the printer delivery extension and make scheduled reports be delivered automatically to a printer and acutally print in landscape?

Please see me original post and let me know if more info. is needed to answer my questions.

Thanks!

Help!

Help,
i have a nt server sp6 with sql sp3 installed and configured by someone
else. in recent weeks our dc/exchange server had a similar problem in where
i had to do a reinstall from scratch and restore from backup.
because of user accounts being recreated i had to go and add the users again
on the sql server.
i decided to reboot the server after completing the task of adding the
users. then the fun began... the server will past the post, no problem, then
when the winnt server logo would appear on the screen with the mouse
cursor...wham the server started to reboot in an endless loop...right at the
same spot, the winnt logo screen and mouse cursor being displayed on the
screen.
I figured i post this here since this happened right after adding the users
in sql.
it looks like a virus at play but none was detected before the server was
rebooted.
has anybody seen this happen before?
can this configuration be saved ?
any help would be greatly appreciated.
thanks
ronaldHi ,
Ask your system administrater to try out this,
I am merely guessing, try this:
get to system using Console Repair Mode and then change
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wi
ndowsNT\CurrentVersion\Winlogon\Auto
AdminLogon to 0
also if that doesn't help, try to go to your %temp% folder and delete
sit*.tmp files, which the Readme says are used to store the passwords.
Thanks
Hari
MCDBA
"ronald" <ronald_padilla@.msn.com> wrote in message
news:ufR2qMIEEHA.3408@.tk2msftngp13.phx.gbl...
> Help,
> i have a nt server sp6 with sql sp3 installed and configured by someone
> else. in recent weeks our dc/exchange server had a similar problem in
where
> i had to do a reinstall from scratch and restore from backup.
> because of user accounts being recreated i had to go and add the users
again
> on the sql server.
> i decided to reboot the server after completing the task of adding the
> users. then the fun began... the server will past the post, no problem,
then
> when the winnt server logo would appear on the screen with the mouse
> cursor...wham the server started to reboot in an endless loop...right at
the
> same spot, the winnt logo screen and mouse cursor being displayed on the
> screen.
> I figured i post this here since this happened right after adding the
users
> in sql.
> it looks like a virus at play but none was detected before the server was
> rebooted.
> has anybody seen this happen before?
> can this configuration be saved ?
> any help would be greatly appreciated.
> thanks
> ronald
>|||thanks guys.
the server was configured with raid 5 and getting to the registry was a
problem. i needed a way to get to the sql data. i used a independant "hd"
from the raid 5 and was able to back up the data to then restore sql .
again thanks
ronald
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:%23AOgoRJEEHA.3016@.TK2MSFTNGP11.phx.gbl...
> Hi ,
> Ask your system administrater to try out this,
> I am merely guessing, try this:
> get to system using Console Repair Mode and then change
>
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wi
ndowsNT\CurrentVersion\Winlogon\Auto[col
or=darkred]
> AdminLogon to 0
> also if that doesn't help, try to go to your %temp% folder and delete
> sit*.tmp files, which the Readme says are used to store the passwords.
> Thanks
> Hari
> MCDBA
>
> "ronald" <ronald_padilla@.msn.com> wrote in message
> news:ufR2qMIEEHA.3408@.tk2msftngp13.phx.gbl...
> where
> again
> then
> the
> users
was
>