Skip to main content

 

Hi All,

 

 

I have a workbench that takes an Intergraph Access Warehouse, massages it, and then writes to a Intergraph SQL Warehouse. In our environment, using windows authentication on the SQL DB, users only have permission to insert into the SQL DB.

 

 

In the workbench, I have 'Use Windows Authentication' set to 'No'. I then use a specific SQL logon that has full rights to the SQL DB.

 

 

When I run the translation, it fails with the following error log:

 

 

 

Using user supplied ODBC DSN 'ELP_Maintenance' as dataset

 

Successfully connected to source dataset 'ELP_Maintenance'

 

GeoMedia SQL Writer: Table 'ELP_UG_URDBox' has IDENTITY column 'ELP_UG_URDBox_ID'

 

Database error: ' Microsoft]9ODBC SQL Server Driver]eSQL Server]CREATE VIEW permission denied in database 'ELP_Maintenance'.'

 

SQL is: 'CREATE VIEW "FME_VIEW_1" AS SELECT oAsset_Status], sAsset_Owner], AAsset_InstallDate], IAsset_Acquisition], AAsset_WorkOrder_Install], dAsset_CapitalizeYear], iAsset_DisposalYear], iURD_Material], RUse_Secondary], eUse_Traffic_Control], fUse_Streetlight], SUse_Fibre], Label_OffsetX], bLabel_OffsetY], bLabel_Rotation], eGIS_DataSource], _GIS_LastModified_By], MGIS_LastModified_Date], dWMS_AddressClosest], rWMS_Neighbhourhood], gUNITID], dCOMPTYPE], ,COMPKEY], ]ToolTip_1], ToolTip_2], ToolTip_3], ToolTip_4], Geometry_XLO], eGeometry_YLO], eGeometry_XHI], eGeometry_YHI], eGeometry] FROM eELP_UG_URDBox]'

 

GeoMedia SQL Writer: failed to create view for 'ELP_UG_URDBox' table

 

A fatal error has occurred. Check the logfile above for details

 

A fatal error has occurred. Check the logfile above for details

 

 

I have had our DBA, who has full rights to the SQL DB through windows active directory, run this process, and the features are written without issue.

 

 

It appears that FME is still using windows authentication to try to write the the DB even though I have specified a different SQL Logon.

 

 

Any info you could provide on this would be fantastic.  Thanks.

For anyone that runs into this issue please file a support case. We do have an issue filed for it: FMEENGINE-9255 however, it remains open at this time.


Reply