Aller au contenu principal

Recherche

Recherche

Print Driver Registy Entries Filling Registry

Commentaires

9 commentaires

  • Avatar
    Legacy Poster

    Did you ever get any information on this issue or a resolution? We are running into the same issue on a Windows 2008R2 RDS server.

     

    0
  • Avatar
    Legacy Poster

    We have exactly the same problem, any idea on this issue ?

    Thanks

    0
  • Avatar
    AlexeyCher

    I have the same problem

    I my case we have problem with millions (im seriously) of keys in

    HKEY_USERS\.Default\Software\Seagull Scientific\Drivers\@CSR|wbp-print\PRINT:\Printers

    We found some smart idea in that place

    http://serverfault.com/questions/568061/2008-r2-terminal-server-insufficient-system-resources-exist-to-complete-the-re

    Hope it help you

     

    0
  • Avatar
    Jasper Wen
    Modérateur

    I would also suggest making sure you are on the latest Seagull Printer driver version. Latest version is currently v7.4.2. I believe there were some known issues with this scenario in previous versions of the driver.

    0
  • Avatar
    AlexeyCher

    Not in my case.

    We have latest version, but today our server reach to max limit of registry size (hive Default grow to 1,9 Gb) and we decide reinstall it, cause other way to resolve this problem - not working...

    Let see how it will be on new system.

    I will monitoring this parameter, and if it repeat - i post here again

    0
  • Avatar
    Scott Milner

    Did anyone ever find a solution to this issue?  I'm having it with a Server 2008 R2 SP1 application server (not RDS).

    AlexeyCher, when you state you 'reinstall it', do you mean you have to do a complete server reinstall?

     

    thanks!

     

    Scott

    0
  • Avatar
    Scott Milner

    Seagull Tech support states that the issue was identified and resolved in version 7.4 of the driver (I was using 7.3).  Has anyone tried this?  If it did fix the issue, were you able to fix the registry by simply deleting the bloated key?

     

    thanks,

     

    Scott

    0
  • Avatar
    Amy Frideger

    Scott Milner, it appears we are having this same issue on our server.  The registry has thousands of lines under Seagull.  The registry is so bloated that our profiles to logon to the server are all temporary.  Did the newer driver fix your issue?  Even if we upgrade the driver how do you fix the registry?  Did you delete the keys?

    Thanks, 

    0
  • Avatar
    Scott Milner

    Hello Amy,

    I ended up compressing the bloated registry hive using this technet article...

    https://support.microsoft.com/en-us/help/2498915/how-to-compress-bloated-registry-hives

    Unfortunately, just deleting the keys isn't an option.  The registry is a database, and if you delete the key, you are only 'zeroing' out the pages within that particular table.  The database retains it's original bloated size, albeit with a lot of 'whitespace' or blank pages.

    I then switched to the latest drivers, and to be on the save side, eventually migrated to a newer print server.  So far, I'm not seeing this issue on my Server 2012R2 print server running the 7.4 version of the Seagull drivers.

    If you have any other questions, let me know.  I'll see if I can dig out some notes I took on the process.

    Scott

    0

Vous devez vous connecter pour laisser un commentaire.