Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread EDBMgr Error
Wed, Apr 30 2014 8:33 AMPermanent Link

Kevin Koehne

I'm getting a "Cannot Create Directory" when I run EDBMgr on a Windows 8 machine. I saw this post
http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_suggestions&msg=493&start=1&keywords=cannot create directory&searchbody=True&forum=EDB_Announce&forum=EDB_General&forum=EDB_SQL&forum=EDB_Connect&forum=EDB_Extensions&forum=EDB_Beta&forum=EDB_Binaries&forum=EDB_Suggestions&forum=EDB_ThirdParty&forum=EDB_Discussion#493

which seems to be a similar issue, but there are no mounted drives on this machine. I'm not sure what directory it's trying to create. I also verified that the user had rights on the AppData folder (I manually created a file and folder in the C:\Users\name\AppData\Local\Elevate Software\ElevateDB Manager to verify).

EDBMgr has never been run on this computer previously.

Any thoughts? Thanks
Wed, Apr 30 2014 10:46 AMPermanent Link

Barry

Kevin,

The best way to track down which file it is trying to create is to download and run ProcMon from SysInternals. You can get a copy here http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx

Run it and set up a filter for EDBMgr.Exe as the process name. Then start EdbMgr.exe and watch to see which files it fails to write to near the bottom of the list. It may be referencing a drive letter that doesn't exist or trying to write to a directory that the user does not have rights to.

Barry
Wed, Apr 30 2014 11:02 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Kevin

Try downloading SysInternals from Microsoft and run procmon (I think it is) and that will tell you what file its trying to open.

If EDBManager has never been run on this machine before, and its a virgin install, its worth seeing if you have rights to the temporary directory (I'm not sure just when that gets opened) or if you've moved it across from another machine then edgmgr.ini could have saved its state before you moved it and it could be trying to open something that just doesn't exist.

Roy Lambert
Thu, May 1 2014 8:31 AMPermanent Link

Kevin Koehne

Thanks. I'll give that a try.
Image