TDP 3.3.0.1526 Now Refuses to Start w "System.IO.IOException - The file exists."

Toad Data Point & Toad Intelligence Central
1

Just starting early this morning, I’m getting the errors below whenever Toad Data Point 3.3.0.1526 attempts to start - either through Automation or by starting it directly. OS is Windows XP SP3:

System.IO.IOException
The file exists.

Stack Trace:
at Quest.Licensing.QuestKeyFactory.QKFInitialize()
at Quest.Licensing.QuestKeyFactory…ctor()
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)

Followed immediately by:

System.ComponentModel.Win32Exception
Invalid window handle
Stack Trace:
at MS.Win32.UnsafeNativeMethods.CreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)
at MS.Win32.HwndWrapper…ctor(Int32 classStyle, Int32 style, Int32 exStyle, Int32 x, Int32 y, Int32 width, Int32 height, String name, IntPtr parent, HwndWrapperHook[] hooks)
at System.Windows.Interop.HwndSource.Initialize(HwndSourceParameters parameters)
at System.Windows.Window.CreateSourceWindow(Boolean duringShow)
at System.Windows.Window.CreateSourceWindowDuringShow()
at System.Windows.Window.SafeCreateWindowDuringShow()
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Window.Show()
at Quest.Toad.Exceptions.Unhandled.ForceApplicationShutdown.ProcessUnhandledExcsAndShutdownApplication_Thread(Object state)
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)

The TOAD.EXE process then appears to orphan (viewable in Task Manager or Process Explorer) until manually killed.

This has prevented over 30 reports from executing and processing, and is creating a huge problem for us as we head into the weekend - the really problematic part, however, is that not all of the reports have failed - just some - but this is the error we get when TDP attempts to start.

2

I should mention that the machine in question has been rebooted since this error has started, and that didn’t change anything.

3

This is some kind of error in our licenseing code. Can delete the files in your profile temp dir? Try that first and if not I will get our licenseing people to look at thsi.

4

I checked with a licensing developer and here is what he said.

“According to Microsoft, the only way this error is raised is if no unique temp file can be found. They use a 16 bit number for their unique names. This allows for 65535 unique names. You have asked the user to clear his temp folder already, so hopefully this will solve the problem.”