Zum Hauptinhalt gehen

Suche

Suche

Printing From Web App Not Working

Kommentare

2 Kommentare

  • Avatar
    Domingo Rodriguez
    Moderator

    When you start BarTender via your web based application, is the bartend.exe process started under a service context? Is it maybe a permission problem while running under this account?

     

    Out of curiosity, do you know that BarTender (in the Enterprise Automation Edition) has a closed web based solution called BarTender Web Print Server?

    http://www.bartenderbarcodesoftware.com/label-software/whitepapers/Web-based-Barcode-and-Label-Printing.pdf

     

    Also, using our .NET Print Server SDKs, you can implement a custom web based solution which makes use of BarTender engines in the background:

    http://www.bartenderbarcodesoftware.com/label-software/whitepapers/Controlling-Barcode-Label-Software-using-C-Sharp-and-VB.NET(English).pdf

    0
  • Avatar
    Legacy Poster

    Yes I think it is a permissions issue.  I am having the same problem.

    I had it fixed and it broke again.

    I was able to "PrintLabel" and I had the web app create a new bartender application in memory.

    Then it used the bartenderFormat.PrintOut(false, false) command.

    I had to set the Application Pool's identity to one that has permissions to run the bartender application locally on the server.

    We have Windows 2008 server running IIS7.

     

    Usually service accounts have restricted I/O permissions due to hackers and security issues.  That may be why you are unable to print with the web application running as the built-in WebAppUser.

     

    Try this in the website configuration:

    Select "Advanced Settings", and Physical Path Credentials.

    Enter a "Specific User" credentials instead of ""Pass-Through Authentication".

     

    I think that is the fix.  I am testing it now as soon as I figure out why it won't takes the password.

    For the application pool, create a new one that has permissions to the File I/O and other system resources.

    Do that by setting the Application Pool's identity to one that an do the above.

     

    Finally in the web config file you can try the "Identity.Impersonate" setting.  I think it is under the security node.

     

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.