topic Re: Operations Dashboard AddIn - License error in ArcGIS Runtime SDK for WPF (Retired) Questions

Operations Dashboard AddIn - License error

MatejVrtich1 — Wed, 30 Oct 2013 07:28:31 GMT

Hi,

While debugging custom Feature Action AddIn for Operations Dashboard, this error message appears:

{"License error with ArcGISRuntime. Main license has expired."}
For detailed info I append the call stack log below.

My development machine is licensed with ArcGIS Runtime SDK Standard license.

Do anybody experience the same issue?

Thank you,
Matej

Call Stack:

ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.Layer.OnInitializationFailed(System.EventArgs e) + 0x11f bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.Layer.Initialize() + 0xd8 bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.GroupLayerBase.AnonymousMethod__FabricatedMethod4() + 0x28 bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.GroupLayerBase.Initialize.AnonymousMethod__0(object a, System.EventArgs b) + 0x54 bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.Layer.OnInitialized(System.EventArgs e) + 0x5d bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.Layer.Initialize() + 0x83 bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.TiledLayer.Initialize() + 0x4b bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.ArcGISTiledMapServiceLayer.AnonymousMethod__FabricatedMethod2b() + 0x28 bytes
ESRI.ArcGIS.Client.dll!ESRI.ArcGIS.Client.ArcGISTiledMapServiceLayer.MapServiceInfoInitialized.AnonymousMethod__30() + 0x1f4a bytes
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) + 0x17c bytes
WindowsBase.dll!MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(object source, System.Delegate method, object args, int numArgs, System.Delegate catchHandler) + 0x47 bytes
WindowsBase.dll!System.Windows.Threading.DispatcherOperation.InvokeImpl() + 0x281 bytes
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) + 0x285 bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) + 0x9 bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x57 bytes
WindowsBase.dll!System.Windows.Threading.DispatcherOperation.Invoke() + 0x71 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.ProcessQueue() + 0x2a1 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.WndProcHook(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) + 0xb3 bytes
WindowsBase.dll!MS.Win32.HwndWrapper.WndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) + 0x14a bytes
WindowsBase.dll!MS.Win32.HwndSubclass.DispatcherCallbackOperation(object o) + 0x80 bytes
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) + 0x5e bytes
WindowsBase.dll!MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(object source, System.Delegate method, object args, int numArgs, System.Delegate catchHandler) + 0x47 bytes
WindowsBase.dll!System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority priority, System.TimeSpan timeout, System.Delegate method, object args, int numArgs) + 0x2bc bytes
WindowsBase.dll!MS.Win32.HwndSubclass.SubclassWndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam) + 0x140 bytes
[Native to Managed Transition]
[Managed to Native Transition]
WindowsBase.dll!System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame frame) + 0x112 bytes
PresentationFramework.dll!System.Windows.Application.RunInternal(System.Windows.Window window) + 0x17a bytes
PresentationFramework.dll!System.Windows.Application.Run() + 0x67 bytes
OperationsDashboard.exe!ESRI.ArcGIS.OperationsDashboard.Internal.App.Main() + 0x76 bytes

Re: Operations Dashboard AddIn - License error

MichaelBranscomb — Mon, 04 Nov 2013 17:40:46 GMT

Hi,

Sorry for the delay in replying - it sounds like your license has expired, or if you've renewed your license then your developer license is confused. Take a look at "C:\Program Files (x86)\ESRI\License10.1.1\sysgen\keycodes" in a text editor. That lists all the license strings on your machine and it's where the LicenseViewer reads it's information from. It's possible that you've ended up with both old and new license strings in that file and the old ones are being read first.

My recommendation is to backup that keycodes file and then edit it to remove the old/expired license info or alternatively delete the file and re-run the Software Authorization Wizard with your developer license key to regenerate the keycodes file.

Cheers

Mike

Re: Operations Dashboard AddIn - License error

TifPun — Tue, 05 Nov 2013 22:19:42 GMT

Hi Matej,

In addition to Mike's comment, please note that the license of Operations Dashboard has expired about 2 weeks ago and you will encounter problems opening/creating an operation view. If you are using the 10.1.1 WPF SDK, you could follow the steps below to get the updated 10.1.1 Dashboard, and use it to replace the expired one:

Uninstall Operations Dashboard from Programs and Features if you have previously installed it from arcgis.com.

Install the updated Dashboard from arcgis.com. This is the build with the license issue fixed. Once completed, the application will launch automatically.

Open the application's file location (Start Task Manager > Go to the Processes tab > Right click on OperationsDashboard.exe > Click Open File Location). The folder containing OperationsDashboard.exe will open.

Copy all the files in the folder and overwrite the ones in the OperationsDashboard folder installed with the WPF SDK (e.g. C:\Program Files (x86)\ArcGIS SDKs\WPF10.1.1\sdk\OperationsDashboard. You can also find this location from the "Start External Program" property in the Debug tab of your project's property page).

When you re-run your addin project locally, it will use the updated Operations Dashboard.

Please note that if you have updated your WPF SDK to 10.2, you should not encounter the above problems. If so, please let us know.

Thanks

Tif