topic Re: Map Services - crosslinked data in ArcGIS Enterprise Questions

Map Services - crosslinked data

LuciHawkins — Thu, 28 Mar 2013 13:27:50 GMT

Hey,

I am experiencing problems with a couple of my map services. It seems as though they are cross-linking data. See ArcGIS 10.1 Server error log:

[ATTACH=CONFIG]23030[/ATTACH]

I am getting an error about layer wFitting in map service FWBWater not drawing. The error right before that one references and "Invalid colunm name 'Subtye' for swFitting in map service FWBWater. Well, swFitting is not even IN the map service FWBWater - it is in map service FWBStormwater.

When I use the "identify" tool in my flexviewer app and click on a swFitting, I get two popups - one for the swFitting data and one for wFitting data - any common field names are populated with the swFitting data in the wFitting popup.

FWBGDBpublic is a SQL database

FWBWater - is a dataset in FWBGDBpublic
wFitting - is a feature class in FWBWater dataset

FWBStormwater - is a dataset in FWBGDBpublic
swFitting - is a feature class in FWBStormwater dataset

NONE of the FWBWater data is in the FWBStormwater map service and NONE of the FWBStormwater data is in the FWBWater map service.

Anyone else ever experience this?

I have deleted the services. Recreated the services and still get the same errors.

Thanks,

Luci

Re: Map Services - crosslinked data

LuciHawkins — Thu, 28 Mar 2013 14:08:13 GMT

Here are screen shots from the two map service rest points:
[ATTACH=CONFIG]23031[/ATTACH]
[ATTACH=CONFIG]23032[/ATTACH]

Here are screen shots from the two datasets in my SQL GDB:
[ATTACH=CONFIG]23033[/ATTACH]
[ATTACH=CONFIG]23034[/ATTACH]

Thanks,

Luci

Re: Map Services - crosslinked data

TomMagdaleno — Wed, 17 Apr 2013 15:58:29 GMT

Have you tried switching from low isolation to high isolation?

Re: Map Services - crosslinked data

LuciHawkins — Mon, 22 Apr 2013 18:29:58 GMT

Well, after several phone calls and several attempts using as many different ways as you can to create a new geodatabase, it seems as though my server just did not like my database name. I used another database name and have not had any problems. FWBGDBpublic - cannot use this name on our sever - FWBPublicGDB - worked just fine - so after repairing data sources on all maps and republishing them everything is working as it should now.

Thanks,

Luci