Ошибка нельзя установить свойство orientation класса pagesetup

• Remove From My Forums

• General discussion

• Hi,

  In the most recent release of a new service, we have a section of code that creates an Excel document and saves it in a location.  Nothing super complicated.  This service uses the 2003 Excel Interops (not my choice — it’s what is passed down
  to us from above as a requirement) to do this.

  Previous to this weekend’s install, the service was installed on Server 2003 and worked perfectly.  The production version that it lives on, however, is Server 2008.  Any time this service tries to create an Excel document it thows the error
  Unable to set the Orientation property of the PageSetup class.  It was not giving this error on 2003.

  After searching online the only things I can find tell me to install a default printer.  Which I did.  It did not fix anything.  The 2003 server didn’t have any installed anyway, so I don’t see this as the hinderance.

  Is this something weird with 2008 not installing the ASPNET user?  Maybe something else that I maybe don’t even know to guess?

  If anyone has any other ideas, they would be greatly appreciated.  At this point I’m at a loss as to what to even try.

  Thanks!

  • Changed type

    Monday, August 2, 2010 1:34 AM
    Duplcated post on the office forum

• Remove From My Forums

• General discussion

• Hi,

  In the most recent release of a new service, we have a section of code that creates an Excel document and saves it in a location.  Nothing super complicated.  This service uses the 2003 Excel Interops (not my choice — it’s what is passed down
  to us from above as a requirement) to do this.

  Previous to this weekend’s install, the service was installed on Server 2003 and worked perfectly.  The production version that it lives on, however, is Server 2008.  Any time this service tries to create an Excel document it thows the error
  Unable to set the Orientation property of the PageSetup class.  It was not giving this error on 2003.

  After searching online the only things I can find tell me to install a default printer.  Which I did.  It did not fix anything.  The 2003 server didn’t have any installed anyway, so I don’t see this as the hinderance.

  Is this something weird with 2008 not installing the ASPNET user?  Maybe something else that I maybe don’t even know to guess?

  If anyone has any other ideas, they would be greatly appreciated.  At this point I’m at a loss as to what to even try.

  Thanks!

  • Changed type

    Monday, August 2, 2010 1:34 AM
    Duplcated post on the office forum

• Remove From My Forums

• Question

• User1325737636 posted

  I have a web application that generates various reports in Excel or in Word and then downloads them to the client where they can be printed.  Even though there is nothing being printed on the web server, I want to properly format the reports
  in terms of page orientation, etc.  Everything is working great with Word.

  In Excel, whenever I try to change the page orientation to Landscape I get:

  COMException (0x800a03ec): Unable to set the Orientation property of the PageSetup class

  The single line of code that is causing this is:

  mySheet.PageSetup.Orientation = Microsoft.Office.Interop.Excel.XlPageOrientation.xlLandscape;

  If I comment out the line everything else works like a champ.  The code also works fine when I test it on my local computer (without the line commented out).

  On the server, the web application runs with the username CCSUser.  I can log onto the server using that username, bring up Excel manually, create some sort of spreadsheet, and set the orientation of that spreadsheet to Landscape.  It works fine.
   It just does not work when I try to do it from my C# code.

  There is no physical printer attached to the server.  The default printer for the account used by the web application is Microsoft XPS Document Writer.  The security permissions on that printer allow me to Print, Manage the Printer, and Manage Documents.

  We had the same problem before our recent upgrade from Windows Server 2000 to 2008.  I had hoped that it might magically go away when we upgraded.  It didn’t.

  What am I doing wrong?

  Thanks.

Я написал следующий код в .Net

excel = New Excel.Application
wBook = excel.Workbooks.Add()
wSheet = wBook.ActiveSheet()
wSheet.PageSetup.Orientation = XlPageOrientation.xlLandscape

Когда я запускаю это из локальной системы, он работает и когда я копирую его на сервер и запускаюсь из службы, предоставляющей следующую ошибку.

Невозможно установить свойство Orientation класса PageSetup

Класс PageSetup Excel должен взаимодействовать с драйверами принтера на сервере. Если нет установленных драйверов принтера или доступа к ним, любые вызовы этого класса с вызовом исключения.

Вы должны убедиться, что на сервере установлен принтер по умолчанию, и установлены драйверы принтера. Кроме того, если вы получаете доступ к этому из ASP.net, есть проблемы с доступом, и вы должны убедиться, что учетная запись ASP.Net имеет разрешение на доступ к принтеру. См. Эту статью, в которой излагаются некоторые из вопросов более подробно: http://support.microsoft.com/?id=291298

В общем случае, если вы используете Office 2007 или более позднюю версию, вам следует избегать автоматизации на стороне сервера, так как это может привести к нестабильному поведению — если возможно, используйте форматы Open XML. См. http://support.microsoft.com/kb/257757

• Remove From My Forums

• Вопрос

• Hi,

  In the most recent release of a new service, we have a section of code that creates an Excel document and saves it in a location.  Nothing super complicated.  This service uses the 2003 Excel Interops (not my choice — it’s what is passed down
  to us from above as a requirement) to do this.

  Previous to this weekend’s install, the service was installed on Server 2003 and worked perfectly.  The production version that it lives on, however, is Server 2008.  Any time this service tries to create an Excel document it thows the error
  Unable to set the Orientation property of the PageSetup class.  It was not giving this error on 2003.

  After searching online the only things I can find tell me to install a default printer.  Which I did.  It did not fix anything.  The 2003 server didn’t have any installed anyway, so I don’t see this as the hinderance.

  If anyone has any other ideas, they would be greatly appreciated.  At this point I’m at a loss as to what to even try.

  Thanks!

  • Изменено

    26 июля 2010 г. 14:42
    formatting