• Verified Answer

    +1  

    Apart from the fact that all backgroud info (such as OS (OES, iPrint appliance), version, description of a problem) is missing:

    that's merely how it should look like on a (in this case rather unpatched) OES box. The SUID bit is to be expected on these four "red" binaries.

  • 0 in reply to   

    My OES Version is OES 2018 SP3. And the problem is that configuring iPrint Driver Store by iManager results in following error:

    Treiberablage konnte nicht konfiguriert werden: Request (SERVER_ERROR) - bad status code (0x500)
    iPrint Lib Error: 0x1000001
    IPP Error: 0x500

    in English: Driver Store could not be configured. sqq.

    Sorry for the long absence during Easter Vacation

    Regards Christoph

  • 0   in reply to 

    Are you actually trying to create a NEW driverstore? If so, this error would be common if address and DNS name specified for the target server can't get resolved properly (forward and reverse). Incorrect hosts file entries would also harm.

  • 0 in reply to   

    Thank You for this tip!

    But I did prove merely this case. Neither the hostname nor the Ip-adress has got any problem. The case ist that if i manually want to configure a driver store iprintvnfg starts without showing options.There bust be something wrong with the binary as it seems. It possibly doesn't adress the correct memory space. For instance: If I type the servers ip-adress in a browser, the OES-Welcome Page appears. even if I type in the server name.. The error must be at the iPrint-side of OES.

  • Verified Answer

    +1   in reply to 

    Do you try to add a new driverstore or do you want to configure an existing one?

    Do you use an iManager instance running on an OES server or a "standalone" edition?

    Which browser on which OS do you use to access iManager?

    Does the WS you use have an iPrint client installed? Which build?

  • 0 in reply to   

    First Question: I try to configure a NEW driver store

    Second Question: The iManager instance is running on a OES 2018 SP3 server

    Third Question: Mozilla Firefox 78 ESR on OES 2018 SP3

    Fourth Question: Yes iPrint Client 6.22

  • 0   in reply to 

    Just tried to dupe this on a pretty current (!) OES2018SP3 tree. Didn't have any issues, but the FF build on this OES box is 115.6.0esr, so it seems your system is way behind as for patches. So, assuming the box in question has the iprint role installed properly, i'd really suggest to patch the system. Other than that you might want to try from a Windows box with a current browser such as FF 115.10.0.esr (i've tried this one with success, too).