can't open my proclaim software

Just got my MacBook Pro repaired by Apple.
Can't open proclaim. i have re-downloaded the software from your site.
Mac OS X Version 10.6.8
help? ideas?
Comments
-
Are you able to post diagnostic logs as per the steps at http://community.logos.com/forums/t/39446.aspx?
0 -
I too have just downloaded the latest update and now cannot open Proclaim, The screen show logging and and then disappears.
I have looked for the logging files as per the instructions but none exist. I can get to Application Support but there is no folder called Proclaim.
/Users/[username]/(~Library)/Application Support/Proclaim/Logging/
I have been using Proclaim for some months now with out a problem. The issue only occurred after the last update. I could not open after that.
0 -
Hi Ian
What version of Mac OS are you running?
I am starting to wonder if there is a problem with the latest update on Mac.
Any other Mac users having problems with the latest update - which I believe is build 1.08.0.0104
Graham
0 -
Is this what you are looking for?
Program Version: 1.8 (1.08.0.0104)
Mac OS Version: 10.6.8
Architecture: x86_64
Model: MacBookPro8,2
Processor count: 8
Time: 2012-12-12 08:55:02 -06:00 (2012-12-12T14:55:02Z)
Installed memory: 4,096 MB
Install path: /Applications/Proclaim.app/Contents/MacOS/lib/Proclaim.Macintosh.dll
Free install space: 345,555 MB
Temp path: /var/folders/5z/5z2nqobOGKexttKT-kKwuk+++TI/-Tmp-/
Free temp space: 345,555 MB
Swap usage: total = 256.00M used = 16.03M free = 239.97M
Error ID: 3816
Error detail: TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Libronix.Utility.Threading.AsyncWorkException: Unhandled exception in asynchronous work. ---> Newtonsoft.Json.JsonSerializationException: Could not find member 'videoParams' on object of type 'UploadJobFileProperties'. Path 'videoParams', line 1, position 7797.
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Libronix.Utility.Windows.Threading.DispatcherAsyncWorker+<Start>c__AnonStoreyE+<Start>c__AnonStoreyF.<>m__1C () [0x00000] in <filename unknown>:0
at Libronix.Utility.Windows.DispatcherUtility+<BeginInvoke>c__AnonStoreyA.<>m__16 (System.Object ) [0x00000] in <filename unknown>:0
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at System.Reflection.MonoMethod.Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo) <0x00187>
at System.Reflection.MethodBase.Invoke (object,object[]) <0x00022>
at System.Delegate.DynamicInvokeImpl (object[]) <0x001a7>
at System.MulticastDelegate.DynamicInvokeImpl (object[]) <0x00033>
at System.Delegate.DynamicInvoke (object[]) <0x00016>
at System.Windows.Threading.DispatcherOperation.InvokeOperation () <0x0003b>
at System.Windows.Threading.Dispatcher.InvokeQueuedDispatcherOperations () <0x000fb>
at (wrapper native-to-managed) System.Windows.Threading.Dispatcher.InvokeQueuedDispatcherOperations () <0x0003b>
0 -
Hi Phil, that's some of what we're looking for. Could you actually attach all of the log files you have in that log file folder, using the paper clip attachment button? And include both the ProclaimError.log and the Proclaim.log? The Proclaim.log has additional information that is useful to us. Thank you.
Once you've attached those log files, could you try following the steps listed in this forum thread to see if it resolves your problem? http://community.logos.com/forums/t/62244.aspx
0