Author Topic: No scan, no updates  (Read 1756 times)

Offline henry albert

  • Newcomer
  • *
  • Posts: 7
    • View Profile
No scan, no updates
« on: January 31, 2023, 11:21:46 AM »
Using Windows 11 and 10. Cannot scan to database. Trying to start it, but nothing happens. No messages, no explanation.

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25020
    • View Profile
    • Camera Bits, Inc.
Re: No scan, no updates
« Reply #1 on: January 31, 2023, 11:31:06 AM »
Using Windows 11 and 10. Cannot scan to database. Trying to start it, but nothing happens. No messages, no explanation.

Which build of Photo Mechanic Plus are you using?

I'd like to see your Photo Mechanic log.  In Photo Mechanic Plus go to the Help menu and choose "Reveal Support Data..." and moments later a Windows Explorer window will come forward with the zipped log file selected.  Use the 'Attachments and other options' link when you're composing your reply to this message and there you'll be able to upload your zipped PM log file.

Thanks,

-Kirk

Offline henry albert

  • Newcomer
  • *
  • Posts: 7
    • View Profile
Re: No scan, no updates
« Reply #2 on: January 31, 2023, 12:52:28 PM »
I went to another computer and started from scratch. Same Windows setup. It looks like it scanned files to the new test database. However, it didn't scan the directories and there is no way to access the files in the database. The build is 6738.

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25020
    • View Profile
    • Camera Bits, Inc.
Re: No scan, no updates
« Reply #3 on: January 31, 2023, 12:52:58 PM »
For a problem like this, I suggest contacting our support folks at:

By email: support@camerabits.com

By phone: +1 503.547.2888

Hours: Mon-Fri, 9:00am-5:00pm [PST/PDT]

Offline henry albert

  • Newcomer
  • *
  • Posts: 7
    • View Profile
Re: No scan, no updates
« Reply #4 on: January 31, 2023, 01:11:14 PM »
Well, it's beginning to look like Operator Malfunction, anyway. Things are looking up, I think.