1 of 1 people found this helpful
Hmmm... certainly sounds a bit strange
Everything you've done sounds fine. I would check the db that ePO is using in the core/config page, and assuming it's the db that you moved then that should be fine.
You can always test it, albeit slightly crudely, by stopping the ePO services, detaching the db in question, and then starting the services again. If you get a load of errors in the orion log and can't log in to epo, then you know you've got the right db
Thanks Joe, I tried your procedure and it responded just like you said. I received multiple errors on the EPO logon screen after detaching the DB and was unable to logon. Upon re-attaching the DB and re-starting all services, I was able to logon to EPO no problem. Thats a big relief, but I am still puzzled as to why the Modify date on the EPO DB isn't changing. I am under the impression that the DB modify date changes anytime something within the DB changes, such as recording a new event. This means the the DB should be changing constantly. Is this correct?
Like I said before everything appears to be working properly, its just this date that is worrying me. Perhaps I am overthinking this...
At least we know you've got the right db
Which file are you talking about? The .mdf file?
Both the .mdf (Database) and .ldf (transaction log).