I have data loaded into a SQL Server 2014. I have validated the connection to the data source in ArcGIS Server 10.4.1.
I can add geographic data to an ArcMap Client and publish to Server.
When trying to view the data from the rest service page the geometry is not displayed and I receive the following error in the Server logs.
There is an error during the draw WISE_Decade_CBAS.DBO.deleteme (1.) DBMS table not found[42S02:[Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Invalid object name 'WISE_Decade_CBAS,(2.) WISLEG\SA-DEV-ARCGIS,(3.) deleteme',(4.) ].
We do not seem to have this same problem in our 10.3.1 environment. I do see the geometry in ArcMap!
I am also not seeing the same behavior in our SDE based environment.
I would guess that this is caused by some sort of permissions issue with the ArcGIS Server Account. Does the ArcGIS Server Account have read privileges to the data in your enterprise geodatabase?
I'm assuming data from a File Geodatabase publishes correctly, and you can view the data?
yes, triple checked permissions with DB admin. This is what he sees when the account connects.
"Login succeeded for user 'WISLEG\sa-dev-arcgis'. Connection made using Windows authentication."
Does the WISLEG\sa-dev-arcgis user also have privileges to the data? For example, did you right-click on the feature class > Privileges and grant read access to this user?
If you are making a connection to your enterprise geodatabase using a Windows Authentication user, then the ArcGIS Server Account will need read privileges to the data to publish successfully. If you are connecting using Database Authentication, then the user will not.
Yes. We can do this!
We found the only way to publish is to run ArcMap as the service account (wisleg\sa-dev-arcgis) and publish. This is our development environment so permissions are not an issue, my operator and user account are db admins. This is just strange.
Is your ArcGIS for Server 10.3.1 environment using the same SQL Server instance or a different, newer SQL Server instance? Also, have you installed the ArcGIS for Server Publishing Patch? On the surface, the patch doesn't seem directly related to your issue, but installing the patch does improve publishing performance overall with 10.4/10.4.1.