The process cannot access the file license.key because it is being used by another process

Hello,

I recently migrated from WinXP Toad Data Analyst 2.7 to Windows 7 Toad Data Point 3.3. I’ve moved about ~30 automated/scheduled jobs, however I intermittently encounter an error when a scheduled job runs. Here’s the error details. I assume this issue occurs when two scheduled jobs run at the same time?

Toad encountered a serious error and must be closed. Please urgently save your data and close the application. Apologies for inconvenience.


IOException

The process cannot access the file ‘C:\ProgramData\Quest Software\Toad Data Point 3.3\license.key’ because it is being used by another process.

Stack Trace:

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)

at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)

at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)

at System.IO.StreamWriter…ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)

at System.IO.StreamWriter…ctor(String path, Boolean append)

at System.IO.File.CreateText(String path)

at Quest.Toad.Map.MapValidation.WriteLicenseFile()

at Quest.Toad.Map.MapValidation.SetCurrentToadOption()

at Quest.Toad.Map.MapValidation.SetOptionsAndCheckIdentity()

at Quest.Toad.Map.MapValidation.Initialize()

at Quest.Toad.Map.MapValidation.get_InstalledPlatforms()

at Quest.Toad.Map.MapValidation.get_InstalledPlatformTypes()

at Quest.Toad.Util.Global.get_MutexAppCode()

at Quest.Toad.StartupForm.Main(String[] args)

Do you have both 2.7 and 3.3 installed at the same Win7 machine? Were you using the 2.7 license key in 3.3? If not, please delete the license.key file, then do a search in App dir and App data dir ( both can be accessed from about box) to see if there’s other license.key files, delete them all should resolve the issue.

Correct - Both 2.7, 3.3, & now 3.4 installed. 2.7 key was used with 3.3. And I’ve since upgraded to 3.4.

Where should the key location reside? And should I delete the other key file locations?

If you are using 2.7 key in 3.3 and 3.4, I’m afraid the license.key file cannot be deleted. Could you obtain a new key from support?