Started by musashi77, September 14, 2020, 04:05:08 PM
Quote1. The log file is virtually empty. It only contains one entry.This cannot be a real log file, or something on your machine is immediately stopping IMWS (Virus Checker, Group Policy etc.).
QuoteDid you try to open a browser on the same PC running IMWS? Does that work?
Quote2. Can you access the share from the PC running IMWS in IMatch?In that case, the user running IMWS has no access to the resource or network at all.But all this would be logged in the IMWS log file, but your log file contains only the first entry written shortly after the log file is opened. IMWS is doing nothing, not even starting up.
QuoteIf something does not work, from experience, it is either:- Name resolution in the network (the PC running IMWS cannot be accessed via its name but only via its IP address - most common in Apple networks)- Virus Checker on the PC running IMWS blocking something- Firewall on the PC running IMWS blocking something
Quote from: musashi77 on September 17, 2020, 03:36:34 PMServer 2012: File Share 'PICS' hosts all my photos. There is a 'user' account with access on this server.Windows 10: This computer has a Mapped drive to the share 'PICS' using the credentials 'user' from the Server.So the issue I have is iMatch anywhere is running under my local user account on Win10, so I created a new local account 'IMWS' and use this to run the service on the Win10 computer, however this ofcourse does not work as the the server doesn't know of the account and therefore can't access the share. The account that does have access resides on the server, but the local computer doesn't know of it so is unable to use. So I'm left with accounts at each location but neither being able to be used on the other.Hope all of this is making sense. So the question I have is how do I get an account on my local that has access required on the server side? I can't figure that part out.
QuoteStill I dont know how I get a account access from this computer?
QuoteEnsure you have an account with the same username AND password on both machines (so if IMWS exists on WIN10 with password 12345, you need a user IMWS on SERVER2012 with password 12345).Make sure the share is accessible to the user.If your files are accessed through a path that won't work (eg a mapped drive - P:\Pictures instead of \\SERVER2012\Share\Pictures\) then setup a relocation rule (Edit->Preferences->Database->Portability Options; add appropriate rules (eg for SERVER2012, relocate P: to \\SERVER2012\Share\Pictures).IMA may take slightly longer to start up the first time (as it'll do the relocate).
Quote from: musashi77 on September 18, 2020, 04:28:37 PMQuoteSo following the above steps, I've got to the "Portability options", and selecting 'Add' does nothing at all. The other problem is I am unable to select the drive in the rules section, whether I select Disk or Folder I am unable to select the top level, and selecting Disk appears to revert to Folder selection (see screenshot)Type the name of the server machine in, eg server2012 - press add, it should then change to uppercase.Click new.Put your source FOLDER or DISK in (eg p:\photos) - if you use the picker, the dashed box is for things NOT in your database (eg the root folder - p:), expand it until you get to a full box (eg p:\Photos)Type the UNC path in the TARGET eg (\\Server2012\PhotoShare\Photos). Do NOT use the picker.Click OK.Click OK.Go back into the dialog and make sure that the relocation options are shown.I just relocate the entire disk (disk p: goes to \\server\share ).Good luck!
QuoteSo following the above steps, I've got to the "Portability options", and selecting 'Add' does nothing at all. The other problem is I am unable to select the drive in the rules section, whether I select Disk or Folder I am unable to select the top level, and selecting Disk appears to revert to Folder selection (see screenshot)