topic Re: Exception from HRESULT: 0x80041538 in ArcGIS Pro Questions

Exception from HRESULT: 0x80041538

AlvinChin1 — Wed, 22 Aug 2018 20:15:13 GMT

I'm trying to add data from an Azure SQL table in an Azure SQL database onto the map in ArcGIS Pro but I'm getting an error:

Add data

Exception from HRESULT: 0x80041538

Why is this the case? My Azure SQL table includes location data which is lat and long, both as numbers. I tried using my local Windows machine and also using a Windows VM hosted in Azure where the Azure SQL database resides.

Re: Exception from HRESULT: 0x80041538

KoryKramer — Thu, 23 Aug 2018 18:30:33 GMT

Geodatabase‌ Anybody have thoughts on this - what to look at?

Re: Exception from HRESULT: 0x80041538

George_Thompson — Thu, 23 Aug 2018 19:13:49 GMT

I think that this one may best be served by contacting technical support.

Re: Exception from HRESULT: 0x80041538

AlvinChin1 — Thu, 23 Aug 2018 21:37:27 GMT

This is something that should be simple to solve. I have read that the table should have OID so I created an id column to be unique, but I am still having this problem of adding data to the map. I even also used the Create query layer, specified the SELECT statement for all records in the table, but still doesn't work.

Re: Exception from HRESULT: 0x80041538

deleted-user-s-XH6KNGak26 — Thu, 29 Nov 2018 03:52:40 GMT

I have the same problem, how could i fix this?

Re: Exception from HRESULT: 0x80041538

CliffParker — Thu, 28 Mar 2019 17:00:37 GMT

Any update on this error? I am also getting this error message. I'm trying to add a spatial view that I created in a SQL database.

Thanks,

Re: Exception from HRESULT: 0x80041538

PatrickChapuis — Tue, 16 Jul 2019 08:58:48 GMT

Does anyone have a solution on this ? I work for two separate clients who are facing this issue. The first one is a recently migrated client (both database and ArcGIS Enterprise) but the second one not had a so important operation recently.

Considering the fact that, if i right click on a table, it proposes me to register with the geodatabase, I suspect there is something to deal with a dysfunctioning in sde.gdb_items...

Re: Exception from HRESULT: 0x80041538

williamlawrence — Thu, 17 Oct 2019 19:52:54 GMT

For me it was because I had spaces in my column names from the view I was attempting to use. I replaced them with underscores and it worked just fine.

Re: Exception from HRESULT: 0x80041538

ShawnRoberts1 — Fri, 13 Dec 2019 15:29:25 GMT

Any follow up on this one? I've got a view that I've really simplified down as I continue to get this error. Even with the most simple view I can do. Even with this I get the HR Result error. The view is stored in an enterprise gdb on SQL server 2019 if that helps in any way. There is no spaces in any field names. Any ideas?

SELECT a.ObjectID, a.ARN,a.SHAPE,b.roll_number
FROM tableA as a
FULL OUTER JOIN tableB as b
ON a.ARN = b.roll_number;

Re: Exception from HRESULT: 0x80041538

JoshuaBixby — Fri, 13 Dec 2019 17:51:52 GMT

The hex code 0x80041538 maps to error -2147216072: FDO_E_SE_DB_IO_ERROR. (https://desktop.arcgis.com/en/arcobjects/latest/net/webframe.htm#fdoError.htm ). Given it appears to be a DB IO error, I suggest you consult your SQL Server logs because there should be some more specific information in the logs about the error.

Re: Exception from HRESULT: 0x80041538

ShawnRoberts1 — Wed, 18 Dec 2019 15:00:45 GMT

Hi Joshua, thanks for the reply. On the SQL end the view is healthy and seems works correctly. Whatever is happening it seems to be happening on the pro side. I can delete the view completely use the "create view" tool in pro and it will either hang up and crash pro or cause the same error. The verbose SQL server logs say the data is provided to pro without a problem. So it seems to be on the pro end.

Re: Exception from HRESULT: 0x80041538

JoshuaBixby — Thu, 19 Dec 2019 15:23:40 GMT

My guess is that it has to do with FULL OUTER JOIN. Although you likely need FULL OUTER JOIN, have you tried other joins with the same columns and condition?

Re: Exception from HRESULT: 0x80041538

ShawnRoberts1 — Thu, 19 Dec 2019 15:44:44 GMT

Thanks for the help Joshua. I had some time to do some testing yesterday. I did try just a left join with the same result (works in SQL Manager fails in pro). I was able to generate another fairly generic error (unable to open table on the attribute table... pretty expected at this point). So I'm getting the feeling that the view is simply just too large for pro to deal with. It's about 70,000 unique parcel geometries. As soon as I take the join out and just do a view of the layer i'm using (CREATE view as select * from table a) as a test it works. However as soon as I add the join back in it fails in pro again (still works perfectly when opening view right out of SQL Manager)

Maybe I'm just not familiar enough with pro but is there a way to put a monitor between pro (or maybe its built into pro) and its databases to watch traffic, and requests to try to catch whatever is happening.

Re: Exception from HRESULT: 0x80041538

JoshuaBixby — Thu, 19 Dec 2019 16:11:31 GMT

I forgot to ask, how exactly are you trying to add the data to Pro? Are you using Make Query Layer? If so, what are the exact arguments?

Re: Exception from HRESULT: 0x80041538

ShawnRoberts1 — Thu, 19 Dec 2019 16:26:30 GMT

No problem. I'm trying two different ways.

The first way I am doing this is creating the view directly out of pro using the create view tool. Then when I try to add the view (either dragging the data in or using the add button), the errors occur.

The second way is I create the view in SSMS and then use the register with database tool in pro. Then add it. Both produce the same result.

I'm doing these a views as this data updated almost daily in our databases, and it needs to be displayed in our portal. I can't just create the in memory join as portal doesn't support that.

Re: Exception from HRESULT: 0x80041538

JoshuaBixby — Thu, 19 Dec 2019 17:24:19 GMT

Since OBJECTID is commonly an Esri geodatabase system field, I would refrain from having your ID fields named the same thing. I am not saying that is the issue here, but eventually it will cause confusion to have user-fields with the same names as common Esri system fields.

At this point, I would open a case with Esri Support. There are more things to check, but doing it via forums gets cumbersome at a certain point.

Re: Exception from HRESULT: 0x80041538

FAdair — Sun, 12 Apr 2020 13:03:01 GMT

Worked for me after converting excel file format to 'Excel 97-2003'.

Re: Exception from HRESULT: 0x80041538

EugeneNamaste — Thu, 16 Apr 2020 02:57:56 GMT

I have this problem after extracting table from an Azure SQL Table into a local SQL Express table and trying to read the output table in ArcGIS Pro. I use Py Pandas to read/write the table and keep the index. Having 'index' field name in the output looks like only one of the reasons -- I rename index to something else. I finally I resolve this issue, a long way and still need to research what exactly causing this. Extracting the same Azure table but writing it to a geodatabase table give me a valid table so then I recreate a blank table using the same schema from the valid geodatabase table minus OBJECTID and its associated properties, then append from Azure SQL table to this table.

Re: Exception from HRESULT: 0x80041538

Raphiki — Wed, 06 Jan 2021 10:19:22 GMT

How did you deduced the int -2147216072 from 0x80041538 ? Is it an hexa to decimal conversion?

Re: Exception from HRESULT: 0x80041538

TheodoreF — Mon, 22 Mar 2021 12:33:57 GMT

I've had this error when adding a layer from a PostgreSQL .sde database connection in ArcGIS Pro (dragging the layer/right click adding from the catalog pane). In PostreSQL, if I create a copy of the table making sure it has a unique id field and only ONE geometry field, it adds to the map just fine.

So it seemed that the error was originally happening when trying to add a layer which had 2 geometry columns. Not sure if that is a cause or not however.