We recently updated some field names, then changed them back after some issues, in one of our Enterprise services.
Looking the map, the layer is fully drawing and all symbology, labels and pop-ups are how they should be.
However in the Server Manager logs, it is spitting out constant errors about the layer saying:
| There is an error drawing layer: *layer name* |
| There is an error during the draw *layer name*. Attribute column not found [42S22:[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid column name *old field name*,(2.) ] [*layer name*][STATE_ID = 12]. |
Is it getting hung up on an old field name? We have already repathed the symbolgy, pop-ups and labels to the current field names as well as in the Visualisation tab of the feature layer (unable to do in the map image)?
Ok I feel like a bit of a goober posting so fast after my original post, but after some more last minute trial and error, I found a solution. In a nutshell, I had to re-add that field that was deleted.
Here was my workflow: re-add that temp field that was deleted but the DB was still looking for, republish map service, open dashboard/server manager and confirm no data errors, delete field, republish map service, and again confirm dashboard/server manager were indeed happy. Hope this is helpful to anyone else running into this issue.
Hi, we just ran into this crazy situation with this error message about a field that doesn't exist in the feature class.
I found out that it had to do with labels. For some strange reason, in the labeling properties (VBscript) a non-existing field name was used, and this provoked the error message.