Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Crash on start
Options
Go to last post Go to first unread
Previous Topic Next Topic
alokgovil  
#1 Posted : Sunday, January 2, 2011 2:16:30 AM(UTC)
alokgovil

Rank: Newbie

Joined: 1/2/2011(UTC)
Posts: 4
Just installed latest version on Windows Vista x32.

This is what I get. Tried the recommended exe installer, as well as USB version.


System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.RijndaelManaged..ctor()
at aZruJ57tnibDhXL6BR.bxURXmwiss68bBpMjM.XjTMxCkyo(Int32 )
at Finkit.ManicTime.Common.Licensing.LicensingConfigurator.Configure(IUnityContainer container)
at Finkit.ManicTime.Tracker.Main.ServiceLocatorConfigurator.ConfigureUnityContainer(StartupArguments startupArguments)
at Finkit.ManicTime.Tracker.Main.ServiceLocatorConfigurator.Configure(String[] args)
at Finkit.ManicTime.Tracker.WinApp.Program.Main(String[] args)


***ProcessInfo:
*** Start: 1/1/2011 4:12:01 PM.949
*ProcessInfoX86 Start: 1/1/2011 4:12:01 PM.950
6.0.6002.131072 X86
---
5460 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\ManicTime.exe
---
11408, (11408, Wait, UserRequest, 1/1/2011 04:11:55.1763): 00:00:01.2636081
System.Threading.WaitHandle.WaitOne
System.Threading.WaitHandle.WaitOne
System.Diagnostics.Process.WaitForExit
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoService.RunAndCaptureOutput
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoService.GetProcessInfo
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoService.GetProcessInfo
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoLog.Write
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoLog.Write
Finkit.ManicTime.Tracker.Main.ExceptionHandling.TrackerExceptionHandler.HandleUnhandledException
Finkit.ManicTime.Tracker.WinApp.Program.HandleUnhandledException
Finkit.ManicTime.Tracker.WinApp.Program.Main

10660, (10660, Wait, UserRequest, 1/1/2011 04:11:55.2443): 00:00:00
11508, (11508, Wait, UserRequest, 1/1/2011 04:12:01.5403): 00:00:00
11428, (11428, Wait, EventPairLow, 1/1/2011 04:12:01.6433): 00:00:00
10816, (10816, Wait, UserRequest, 1/1/2011 04:12:01.9913): 00:00:00.0156001

12020, (12020, Wait, Executive, 1/1/2011 04:12:02.0843): 00:00:00.0312002
[Internal thisFrame, 'M-->U', Microsoft.Win32.Win32Native::ReadFile]
System.IO.FileStream.ReadFileNative
System.IO.FileStream.ReadCore
System.IO.FileStream.Read
System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage
System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall
System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack
System.Threading._ThreadPoolWaitCallback.WaitCallback_Context
System.Threading.ExecutionContext.Run
System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback




*ProcessInfoX86 End: 1/1/2011 4:12:02 PM.804

*** End: 1/1/2011 4:12:02 PM.805

Edited by user Sunday, January 2, 2011 10:19:09 PM(UTC)  | Reason: Not specified
Back to top
admin  
#2 Posted : Sunday, January 2, 2011 10:23:13 AM(UTC)
admin

Rank: Administration

Joined: 4/13/2010(UTC)
Posts: 872
If you are allowed to, try changing the Use FIPS compliant algorithms for encryption, hashing, and signing setting.

You can change this setting in Control Panel -> Administrative Tools -> Local Security Policy
Disable the setting for "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing"

Does this help?
Back to top
alokgovil  
#3 Posted : Sunday, January 2, 2011 10:17:00 PM(UTC)
alokgovil

Rank: Newbie

Joined: 1/2/2011(UTC)
Posts: 4
I disabled this setting for testing.

Now I get the following error instead. Note that I replaced the portion of the path of the file with XXXX..., but I did keep the file path string length the same.

System.Data.SqlServerCe.SqlCeException: The file resolves to a path that is too long. The maximum length is 260 characters. [ File name = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\Data\ManicTime.sdf ]
at System.Data.SqlServerCe.SqlCeEngine.ProcessResults(IntPtr pError, Int32 hr)
at System.Data.SqlServerCe.SqlCeEngine.CreateDatabase()
at Finkit.ManicTime.Common.SqlCeDatabaseUpdater.CreateDatabase(String password)
at Finkit.ManicTime.Tracker.Main.DatabaseStartupChecker.CreateDatabase()
at Finkit.ManicTime.Tracker.Main.DatabaseStartupChecker.CheckDatabase()


***ProcessInfo:
*** Start: 1/2/2011 12:11:10 PM.634
*ProcessInfoX86 Start: 1/2/2011 12:11:10 PM.636
6.0.6002.131072 X86
---
13908 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\ManicTime.exe
---
14216, (14216, Wait, UserRequest, 1/2/2011 12:11:00.7633): 00:00:03.9000250
System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner
System.Windows.Forms.Application.ThreadContext.RunMessageLoop
System.Windows.Forms.Application.Run
Finkit.ManicTime.Tracker.Main.TrackerApplicationInstance.Run
Finkit.ManicTime.Tracker.WinApp.Program.Main

12608, (12608, Wait, UserRequest, 1/2/2011 12:11:00.8443): 00:00:00
13680, (13680, Wait, ExecutionDelay, 1/2/2011 12:11:07.1393): 00:00:00
13948, (13948, Wait, EventPairLow, 1/2/2011 12:11:07.2373): 00:00:00
14136, (14136, Wait, UserRequest, 1/2/2011 12:11:10.2803): 00:00:00

12384, (12384, Wait, UserRequest, 1/2/2011 12:11:07.6783): 00:00:00.2652017
System.Threading.WaitHandle.WaitOne
System.Threading.WaitHandle.WaitOne
System.Diagnostics.Process.WaitForExit
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoService.RunAndCaptureOutput
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoService.GetProcessInfo
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoService.GetProcessInfo
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoLog.Write
Finkit.ManicTime.Common.ProcessInfo.ProcessInfoLog.Write
Finkit.ManicTime.Tracker.Main.ExceptionHandling.TrackerExceptionHandler.HandleUnhandledException
Finkit.ManicTime.Tracker.Main.DatabaseStartupChecker.CheckDatabase
Finkit.ManicTime.Tracker.Main.TrackerApplicationInstance.<Run>b__0
Finkit.ManicTime.Common.ThreadHelper.<>c__DisplayClass1.<QueueUserWorkItem>b__0
System.Threading._ThreadPoolWaitCallback.WaitCallback_Context
System.Threading.ExecutionContext.Run
System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback

12292, (12292, Wait, Executive, 1/2/2011 12:11:10.7263): 00:00:00
[Internal thisFrame, 'M-->U', Microsoft.Win32.Win32Native::ReadFile]
System.IO.FileStream.ReadFileNative
System.IO.FileStream.ReadCore
System.IO.FileStream.Read
System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage
System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall
System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack
System.Threading._ThreadPoolWaitCallback.WaitCallback_Context
System.Threading.ExecutionContext.Run
System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback




*ProcessInfoX86 End: 1/2/2011 12:11:11 PM.675

*** End: 1/2/2011 12:11:11 PM.675

Edited by user Sunday, January 2, 2011 10:18:28 PM(UTC)  | Reason: Not specified
Back to top
alokgovil  
#4 Posted : Monday, January 3, 2011 6:56:09 AM(UTC)
alokgovil

Rank: Newbie

Joined: 1/2/2011(UTC)
Posts: 4
The last error message was "The file resolves to a path that is too long. The maximum length is 260 characters":

While the path length is much less than 260 to begin with, I still moved ManicTime (USB version) to a different folder so that the path length was very small now. I still get the same error.
Back to top
admin  
#5 Posted : Monday, January 3, 2011 11:59:18 AM(UTC)
admin

Rank: Administration

Joined: 4/13/2010(UTC)
Posts: 872
Is this a normal disk or is it mapped to somewhere? Maybe a Ram drive? Anything out of the ordinary?
Back to top
alokgovil  
#6 Posted : Monday, January 3, 2011 8:26:39 PM(UTC)
alokgovil

Rank: Newbie

Joined: 1/2/2011(UTC)
Posts: 4
Totally ordinary disk. Nothing special.

Working from a non-administrator login (normal) on Windows Vista x32, with all latest patches.

4 GB physical RAM

.NET etc. is all installed and has all updates.
Back to top
admin  
#7 Posted : Tuesday, January 4, 2011 10:31:10 AM(UTC)
admin

Rank: Administration

Joined: 4/13/2010(UTC)
Posts: 872
Do you have any other disk?

Could you try running usb version from some short path on other disks like d:\MT\
Could you also try to run it from USB drive if you have any.
Back to top
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2024, Yet Another Forum.NET