Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by bmenk

  1. We've started seeing very slow performance recently using the Daminion client. We run on a Windows server 2016 vm server with 24gb RAM & 4 cpu's. Images are stored on a network share. We have 266K tiff files in the catalog. No changes to either Daminion or the client in several months. IT says we're not making any excessive RAM demands in normal usage. I do see this error in the windows logs going back further than our present sluggish behavior so I don't know if it's related or not: Source: Microsoft-Windows-CAPI2 Event ID: 513 Task Category: none Level: Error Description: An error occurred in Cryptographic Services while processing the OnIdentity()call in System Writer Object. Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol. Thanks for any help. Bobb Menk MIT Lincoln Laboratory Library
  2. We're running server 6.7.0/2312 and our admin user is having issues with the presets for her general tags presets. When she attempts to customize them she sees only "Folders, Media Format, Software". She used to have "File name and media format" available. Also each time she opens the client her customized list of presets has to be rebuilt from scratch. Is there somewhere on the client pc that could be causing this behavior? Thanks Bobb Menk MIT Lincoln Laboratory Library
  3. Checking Daminion server logs instead of Windows logs I'm seeing this error: 2020-11-18 09:55:28,802 [13] ERROR PicaJet.Daminion.Service.Utils.GetTotalRecordsInCatalogCommand [(null)] - Error: (9) Npgsql.NpgsqlException: canceling statement due to statement timeout Severity: ERROR Code: 57014 A timeout has occured. If you were establishing a connection, increase Timeout value in ConnectionString. If you were executing a command, increase the CommandTimeout value in ConnectionString or in your NpgsqlCommand object.
  4. We're running server 6.0.2 build 1904 on a Windows 2016 server. After nightly server patching we got an error that a call to SSPI had failed which seemed to indicate the need to add TLS 1.2 to the host. We did that and rebooted the server and restarted Daminion. Now when we try to connect with the client, we're getting a socket closure error: "The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was 00:59:59:9465424" An existing socket was forcibly closed by the remote host." I have a screen snp of the full error dump if that helps diagnosing this. Any suggestions how we can fix this? Thanks in advance for your help. Bobb Menk MIT Lincoln Laboratory Library
  5. Thanks to both of you for the advice. This should be enough for us to go on. Bobb Menk
  6. We preserve the original Exif modfication dates by checking that option in our server preferences. We would like to find a way to do a monthly search to get the number of records that have been modified by staff. It looks like the exif tool might be able to do this, but there doesn't seem to be any documentation for using it to search specifically for XMP data. Can anyone point me in the right direction for using it to query XMP modify date without also looking at EXIF modified date? Thanks. Bobb Menk
  7. No thoughts or advice on whether or not we can uninstall Ghostscript and just run the client without it? Bobb Menk
  8. Thanks Murat. Checking with our Daminion users, we are not using any vector graphics, only bitmap/raster. If IT security insists on either upgrading or uninstalling Ghostscript (and they might do that) 1. Would that cause any trouble for the Daminion client as long as we aren't doing vectors? 2. If we were to ever decide we needed to handl;e vectors, would a Daminion client upgrade or re-install put the required Ghostscript version back in place for us? Thanks. Bobb
  9. Our IT security folks are requesting the I upgrade Ghostscript from v9.18 - which was installed by the Daminion client to Ghostscript 9.27 (64 bit). Can I just download and run the Ghostscript installer? Or do I need to do something special to keep it "Daminion aware"? Thanks Bobb Menk MIT Lincoln Laboratory Library
  10. Appears to have been cause by the hard drive filling up. I think we're ok for the present.
  11. Since completing our upgrade to 6.02 we've begun to get the errors shown in the screen snap below. Staff are completely unable to use the server at present so help would be greatly appreciated! Bobb Menk
  12. Thanks for the response Uwe. Sadly, There is no EditWithSettings section in the old settings.xml file. You can see the sections available in the screen snap below. Certainly SearchPatternLogSettings and LayoutSettings have quite a bit of data in them that look like they hold quite a few customizations. The ActionSetSettings has a lot of data in it as well in the nested SerializedActionSets section. Those seem to be the sections with the most data. Any advice on which of these contain the most important kinds of settings? Thanks. Bobb Menk
  13. I can see the settings.xml file at that location. I tried copying it from an install using the 4.x client into one using the 6.x client to see if that would bring them across, but it doesn't appear to have done so. Any other ideas on this? Perhaps I need to transfer other files in addition to the settings.xml file? Thanks Bobb
  14. When I point an existing 4.x client at the new Netcatalog at a 6.x server, it forces a client upgrade as expected. However once the client is upgraded all of the customizations that were in the 4.x client are gone. I don't see anything in the old 4.x server backups that allows for backing up client customizations - perhaps that was not available back in 4.x? Would those have been stored someplace like c:\user\myname\daminion on the individual user's machines? If so could they be backed up from that location and restored once the new client is in place? Thanks Bobb Menk MIT Lincoln Laboratory Library
  15. Thanks Uwe! I was able to adapt what you sent me and get a backup working. I laid out the errors I found in the documentation and the zip file download in detail in hopes that someone at Daminion would be able to correct them so the confusion doesn't spread to others. Hope they do that. Bobb Menk
  16. I'm trying to finish off a server migration and can't get the backup batch files to run on the new host. I downloaded the "How to backup" zip file and have some questions. I edited "Backup Daminion Settings.bat" and backup_thumbnails.bat to reflect the path to my backup directory (C:\Users\Public\DaminionBackups\%DATETIME%), etc. I set the username, pw and port to reflect my install in the postgresql_config.bat. However the online instructions at https://daminion.net/tutorials/how-to-backup-daminion-server say to edit the postgres connection info in something called backup_config.bat which is not included in the zip package. Is that different than the postgresql_config.bat? Looking at "Backup Daminion catalog.bat" I can see that it calls postgresql_config.bat on line 12 - I don't see any references in the "backup daminion catalog.bat" to anything called backup_config.bat. The instructions included in the zip file at "Daminion Server Backup-Restore User Guide.txt" aren't the same as the ones online. In that text file it says to edit postgresql_config.bat and then run a file called "dump_postgresql.bat" - which is not included in the zip file either. When I run "backup daminion catalog.bat" it just errors out and says it can't find postgresql_config.bat and dies. postrgresql_config.bat is in the same directory as "backup daminion catalog.bat" (C:\Users\svc-daminion-service\Documents\Daminion_batches) So which process should I be using - the one online or the one included in the zip file instructions? If I'm supposed to follow the online ones I'll need a copy of backup_config.bat. If I'm supposed to follow the one in the zip file I'll need the "dump_postrgesql.bat" file. Thanks for your help. Bobb Menk MIT Lincoln Laboratory Library
  17. We're getting ready to move our Daminion server to a new host and upgrade from 4.1.0 build 1269 to the current 6.x release. To plan that move I'm trying to understand the preferred process. I was thinking of following the process outlined in the "migrate Daminion Server to a new computer", which seems pretty straight forward for getting a copy on the new host. But I have some additional questions about then doing the actual upgrade. If I run the installer for 6.x on top of an existing 4.1 that should take care of the Daminion app itself - but does it take care of the PostrgesSQL upgrade as well? Or does that have to be done separately? Any know troubles going from 4.1.0 to 6.x that folks have encountered? Thanks in advance. Bobb Menk MIT Lincoln Laboratory Library
  18. Thanks Murat! We don't plan to kill off the old network drive, but continue running the two together within the existing catalog. Sounds like we might be best off in that case just mounting the new network drive as a folder within the existing one, rather than changing the properties of the existing catalog to point to a new path. Bobb
  19. How would we add the 2nd network drive to the configuration of the server? I just looked at preferences, catalogs, etc. and couldn't see where that location gets defined.
  20. We would be keeping the existing drive and adding the new one in parallel.
  21. We're running Server on a Windows Server 2008 instance. The images are stored on a network share that is mapped as a drive on the server. We need more space and want to know the best way to connect the additional space to the server. We could mount the new space as a folder within the existing network share so that it would all appear to Daminion as one seamless space. We're also wondering if it's possible to just map the new space to a different drive letter and have the Server be able to see both at once. Is that possible? And what effect might that have on our shared catalogs? Would that just be 2 separate catalogs? Or something else? Thanks. Bobb Menk
  22. It was just a slow read through the database evidently. It finally came up and all seems well. Excellent cardiovascular workout there ;) Bobb
  23. I'm running the upgrade/install for server and all seems well - expect: it's been showing "Start Pending" for about 10 minutes. It is seeing the PostrgreSQL server ok and seems connected there. I'm wondering if it's taking a long time to run through the PostgrSQL data - we have several 100K records in there. Or is it well and truly hung up and I should kill it and try again? Thanks Bobb Menk [email protected]
  24. If we turn on the accelerated preview option on our server side, do our existing images have to be re-imported to build those thumbnails? Or is there another way to get them created? Also is there a good rule of thumb for estimating how much disk space they will take up on the server's local hard drive? (If that's where they get stored). We have hundreds of thousands of images on a networked storage device and would like to be able to estimate how much space that means on the server's hard disk. Thanks. Bobb Menk
  25. We're running our server on a VM which is attached to a large networked storage device and we're seeing occasionally odd behavior that may be permissions related. The server attaches to the storage using a service account. It has Read & Execute, List, & Read permissions. The group of admin Daminion users who map to this same network storage device also have the Modify right. Does the account that connects the server to the storage also need Modify permissions for all that data? Thanks. Bobb Menk
  • Create New...