| T O P I C R E V I E W |
| netizenk |
Posted - 13 Oct 2006 : 06:54:13
Just upgraded to 5.4.3 and when I start the program I get the follwing message:
"Unhandeled exception has occured in your application. If you click Continue the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
Operation is not allowed when the object is closed."
If I click on Continue the porgram loads but I have to manually open the database and than the message appears again when I try to open the database and it won't go away..
I'll try rebooting and will let you know if problem goes away...
Details:
"See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x800A0E78): Operation is not allowed when the object is closed.
at ADODB.RecordsetClass.Close()
at eXtreme_Movie_Manager.mFrmMain.CARICA_MINI_STATISTICHE()
at eXtreme_Movie_Manager.mFrmMain.mFrmMain_Activated(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnActivated(EventArgs e)
at System.Windows.Forms.Form.set_Active(Boolean value)
at System.Windows.Forms.Form.WmActivate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
eXtreme Movie Manager
Assembly Version: 5.4.3.0
Win32 Version: 5.4.3.0
CodeBase: file:///C:/Program%20Files/eXtreme%20Movie%20Manager/eXtreme%20Movie%20Manager.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
ADODB
Assembly Version: 7.0.3300.0
Win32 Version: 7.10.3077
CodeBase: file:///C:/WINDOWS/assembly/GAC/ADODB/7.0.3300.0__b03f5f7f11d50a3a/ADODB.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box." |
| 7 L A T E S T R E P L I E S (Newest First) |
| MTS |
Posted - 15 Oct 2006 : 15:12:16
It was just a suggestion to go back to previous version of XMM so to stop the problem for the time being.
If you didnt like you could just ignore it.
By replying that way, all that you did was to show how kind you are.
Flaming someone, who is only trying to help, even if the solution or workaround is wrong or irrelevant with your problem... is at least STUPID.
So in any case, even if you were right, you lost it by replying that way.
Thanx for reading. |
| netizenk |
Posted - 14 Oct 2006 : 23:34:36
quote:
Originally posted by Markstar
quote:
Suggested workaround by whome?
Who wants to know what you have in your clunker?
Who needs two parapgraph instruction on how to use the stupid System Restore?
Get lost...
Wow, you bash someone who tried to help you? Wow, how mature of you. It is actually you who should get lost. 
Help me? How? With lengthy instructions on how to run stupid M$ System Restore all bundled with 10 rows of purple intestines of his clunker!?
I don't need that kind of help, especially when I'm reporting a bug in a third party software to software developer...
Let me ask you something... If you had a problem with your car's engine that was pissing you off but you knew it only required one part to be replaced, would you like to have some clown show up and try to persuade you that the suggested workaround is to replace the whole engine?
If you would and you'd have all the patience in the world to explain to that clown that your engine doesn't need to be replaced and instead only needs one part replaced, I can only admit that you are a gentleman and a scholar and a much more noble human being than I am...
However, please DO NOT try to take away my Bill Gates given right to tell the clown that he is stupid and needs to get lost...
Just have to love these Saturdays when you get 60 seconds extra to engage in a meaningfull dialogue with a fellow human being.
BTW, 5.4.4 fixed the problem and it looks like I didn't have to replace the whole engine after all... |
| Markstar |
Posted - 13 Oct 2006 : 23:45:10
quote:
Suggested workaround by whome?
Who wants to know what you have in your clunker?
Who needs two parapgraph instruction on how to use the stupid System Restore?
Get lost...
Wow, you bash someone who tried to help you? Wow, how mature of you. It is actually you who should get lost. |
| netizenk |
Posted - 13 Oct 2006 : 23:41:52
quote:
Originally posted by Alessio Viti
Sorry guys, I have found the problem. it's a stupid bug, I am uploading the new 5.4.4.0 just now...
Thanks for the prompt fix Alessio...
D. |
| netizenk |
Posted - 13 Oct 2006 : 23:40:14
quote:
Originally posted by ditto
This is a suggested workaround:
Go to Start --> All Programs --> Accessories --> System Tools --> System Restore and choose the option: "Restore my computer to an earlier time....". You'll get a calendar from which you can choose a "Restore Point". Choose a date & time prior to the error occurring. The operating system will reboot and wind the clock back to that date whereby you should be back to v5.4.2.0
Ideally, you should create a Restore Point before you update or install any program because although the system creates regular Restore Points, it doesn't create them on a daily basis. So if you're forced to choose a Restore Point from say 3 days ago and have installed or updated other programs since then, then those will also have to be reinstalled. This includes security patches from the Windows Update site.
Mobo: DumgF*****Idiot nForce4 SLi-DR
CPU: IMDumb 64 3800+ rev.E3
RAM: 2x512MB CoarsHair TwinX1024-3200XL
Graphics card: HISterectomy X800XL Ice-Q PCI Express 256MB RAM
HD: Dumbgate 7200.8 250gb SATA
PSU: Enerdumb CoolerGiant 600W
OS: Windumbo XP Pro+SP2
Suggested workaround by whome?
Who wants to know what you have in your clunker?
Who needs two parapgraph instruction on how to use the stupid System Restore?
Get lost... |
| Alessio Viti |
Posted - 13 Oct 2006 : 10:32:54
Sorry guys, I have found the problem. it's a stupid bug, I am uploading the new 5.4.4.0 just now... |
| ditto |
Posted - 13 Oct 2006 : 09:36:54
This is a suggested workaround:
Go to Start --> All Programs --> Accessories --> System Tools --> System Restore and choose the option: "Restore my computer to an earlier time....". You'll get a calendar from which you can choose a "Restore Point". Choose a date & time prior to the error occurring. The operating system will reboot and wind the clock back to that date whereby you should be back to v5.4.2.0
Ideally, you should create a Restore Point before you update or install any program because although the system creates regular Restore Points, it doesn't create them on a daily basis. So if you're forced to choose a Restore Point from say 3 days ago and have installed or updated other programs since then, then those will also have to be reinstalled. This includes security patches from the Windows Update site.
Mobo: DFI nForce4 SLi-DR
CPU: AMD 64 3800+ rev.E3
RAM: 2x512MB Corsair TwinX1024-3200XL
Graphics card: HIS X800XL Ice-Q PCI Express 256MB RAM
HD: Seagate 7200.8 250gb SATA
PSU: Enermax CoolerGiant 600W
OS: Win XP Pro+SP2
|
|
|
