Return
-
Title
Error en el cliente Spotlight 10.5.1 cuando se selecciona una conexion SQL Sever. -
Description
1-Al dar click en cualquier conexion SQL Server en v10.5.1, Spotlight mostrara algunos de los siguientes errores:
Error A:"Spotlight on SQL Server has stopped working"Stack trace:Problem signature:Problem Event Name: CLR20r3Problem Signature 01: spotlight.exeProblem Signature 02: 10.5.1.7383Problem Signature 03: 53d5f3c4Problem Signature 04: System.Reactive.CoreProblem Signature 05: 2.2.4.0Problem Signature 06: 535f3abcProblem Signature 07: 36Problem Signature 08: aProblem Signature 09: System.IO.FileLoadExceptionOS Version: 6.1.7601.2.1.0.272.7Locale ID: 1033Additional Information 1: 0a9eAdditional Information 2: 0a9e372d3b4ad19135b953a78882e789Additional Information 3: 0a9eAdditional Information 4: 0a9e372d3b4ad19135b953a78882e789Error B:Message:An unexpected problem has occurredIt is recommended that you send a support bundle to Quest Software. Click "Show details..." for more information about the problem.Details:Details:Handling notification: 13 (0000000D)Parameter info1: UnknownParameter info2: nullMessage:Could not load file or assembly 'System.Core, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes' or one of its dependencies. The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)Source:00D0B8DA (Spotlight.0090A8DA) 10.5.1.7383Call stack:00D0B8DA (Spotlight.0090A8DA) 10.5.1.73830040C4D2 (Spotlight.0000B4D2) 10.5.1.738300D0B8DA (Spotlight.0090A8DA) 10.5.1.738300D0BC08 (Spotlight.0090AC08) 10.5.1.738300D7CBE0 (Spotlight.0097BBE0) 10.5.1.738300D7C82B (Spotlight.0097B82B) 10.5.1.73830080B08A (Spotlight.0040A08A) 10.5.1.73830080B2E9 (Spotlight.0040A2E9) 10.5.1.738300D94570 (Spotlight.00993570) 10.5.1.738300F47F3F (Spotlight.00B46F3F) 10.5.1.738300F48788 (Spotlight.00B47788) 10.5.1.738300F51425 (Spotlight.00B50425) 10.5.1.7383005A57F4 (Spotlight.001A47F4) 10.5.1.7383005AA154 (Spotlight.001A9154) 10.5.1.73830057406A (Spotlight.0017306A) 10.5.1.738300E094DC (Spotlight.00A084DC) 10.5.1.738300ACED86 (Spotlight.006CDD86) 10.5.1.7383004623DA (Spotlight.000613DA) 10.5.1.7383760C62FA (USER32.000152FA) 6.1.7601.17514760C6D3A (USER32.00015D3A) 6.1.7601.17514760C77C4 (USER32.000167C4) 6.1.7601.17514760C788A (USER32.0001688A) 6.1.7601.175140057D25C (Spotlight.0017C25C) 10.5.1.73832. El visor de eventos de Windows puede capturar los siguientes windows Logs:Log Name: ApplicationSource: Application ErrorDate: 8/13/2014 4:21:17 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: <computer name>Description:Faulting application name: Spotlight.exe, version: 10.5.1.7383, time stamp: 0x53d5f3c4Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8aException code: 0xe0434352Fault offset: 0x0000c41fFaulting process id: 0xc20Faulting application start time: 0x01cfb73c7f1d4fb0Faulting application path: C:\Program Files (x86)\Quest Software\Spotlight on SQL Server\Console\Spotlight.exeFaulting module path: C:\Windows\syswow64\KERNELBASE.dllReport Id: c2c26360-232f-11e4-ae45-90b11c353f66Log Name: ApplicationSource: .NET RuntimeDate: 8/13/2014 4:21:16 PMEvent ID: 1026Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: <computer name>Description:Application: Spotlight.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.IO.FileLoadExceptionStack:at System.Reactive.PlatformServices.DefaultExceptionServices.Rethrow(System.Exception)at System.Reactive.ExceptionHelpers.Throw(System.Exception)at System.Reactive.Linq.ObservableImpl.Timer+TimerImpl.InvokeStart(System.Reactive.Concurrency.IScheduler, System.Object)at System.Reactive.Concurrency.DefaultScheduler+<>c__DisplayClass4`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<Schedule>b__3(System.Object)at System.Reactive.Concurrency.ConcurrencyAbstractionLayerImpl+Timer.Tick(System.Object)at System.Threading._TimerCallback.TimerCallback_Context(System.Object)at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)at System.Threading._TimerCallback.PerformTimerCallback(System.Object)3. Ir a "Configure | Alarm Actions" no presentara ningun error.4. Seleccionar las conexiones Windows no presentara ningun error.5. El puerto TCP 40403 esta abierto en el Diagnostic Server
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.