After updating from AIMS 2013 to AIMS 2017 no raster images were shown. Any preview in Studio triggered the following error message in the log file:
<2016-09-07T08:33:35> 3752 Ajax Viewer 10.99.66.114
Administrator
Error: Stilisierung von folgendem Layer fehlgeschlagen:
Luftbild_1pro
Ausnahmefehler in FDO-Komponente aufgetreten.
Ausnahmefehler
in FDO-Komponente aufgetreten.
'FdoATILSession::GetImage': Funktion kann
aufgrund eines ungültigen Wertes für Eingabeparameter 'fileDescriptor' nicht
ausgeführt werden. (Ursache: , grundlegende Ursache: 'FdoATILSession::GetImage':
Funktion kann aufgrund eines ungültigen Wertes für Eingabeparameter
'fileDescriptor' nicht ausgeführt werden. )
StackTrace:
-
MgMappingUtil.StylizeLayers() Zeile 899 Datei
e:\build\2017\re_ims2017_46_1-6376417\ent\os\server\src\services\mapping\MappingUtil.cpp
This message was new to me and hadn't occurred with AIMS 2013.
Also, "Testing connection" always returned "OK" for our raster file data source. The raster file data source uses an ALIAS which points to a shared network drive.
Problem was, that AIMS 2017 was running under local user account. In order to access the network drive AIMS service needs to run under different user account.
AIMS 2017, SP1
About things that happened to me at work.
Showing posts with label error message. Show all posts
Showing posts with label error message. Show all posts
Monday, 19 September 2016
Friday, 7 August 2015
Guest user/role - strange issue #2, solved
As mentioned yesterday we encountered a strange issue related to guest users/roles. Basically it seemed that it is not possible to create a new feature (no matter for which feature class) when working with an guest user/role in our job enabled LandManagement industry model. Instead my colleague got an error message regarding a missing spatial index. Confusing was, that it seemed to work when using a Map-Admin user. Further confusion was caused by the fact that when working directly on the data user the problem did not occur either. When I performed a test on my computer I was not able to reproduce the issue at all.
As it turns out our testing was not so comprehensive as it should have been in the first place and with hindsight the behaviour we observed can be explained.
Culprit seems to be a setting in Map's Global Enterprise Industry Model options (setting is replicated in IM options) : "Vicinity For Digitising Points [m] "
If "Vicinity For Digitising Points [m] " is turned on we get the error message, otherwise we don't. The setting itself is probably not to blame - we actually misunderstood the meaning of the option and can now safely turn it off. I think the option will cause Map to look through all point feature classes and if one of them doesn't have a spatial index one will get the error message.....
The issue is not related to topologies or guest user or non Map-Admin user. As we used different Map users and different industry models (data or guest user) during testing the aformentioned option was not uniformly set, caused therefore different results.
Map 2013, SP2
As it turns out our testing was not so comprehensive as it should have been in the first place and with hindsight the behaviour we observed can be explained.
Culprit seems to be a setting in Map's Global Enterprise Industry Model options (setting is replicated in IM options) : "Vicinity For Digitising Points [m] "
If "Vicinity For Digitising Points [m] " is turned on we get the error message, otherwise we don't. The setting itself is probably not to blame - we actually misunderstood the meaning of the option and can now safely turn it off. I think the option will cause Map to look through all point feature classes and if one of them doesn't have a spatial index one will get the error message.....
The issue is not related to topologies or guest user or non Map-Admin user. As we used different Map users and different industry models (data or guest user) during testing the aformentioned option was not uniformly set, caused therefore different results.
Map 2013, SP2
Subscribe to:
Posts (Atom)