SSMA for Access - How can I figure out exactly what table and column or index these warning messages pertain to?

Question

SSMA for Access - How can I figure out exactly what table and column or index these warning messages pertain to?

A2SS0030 Identifier name might cause problems A2SS0030: Foreign key '{5A15D9A6-64CE-44B3-AD29-21EAF86F0328}' has a name that might cause problems for the Access application to function correctly against SQL Server.
A2SS0030 Identifier name might cause problems A2SS0030: Index '{5A15D9A6-64CE-44B3-AD29-21EAF86F0328}' has a name that might cause problems for the Access application to function correctly against SQL Server.
A2SS0030 Identifier name might cause problems A2SS0030: Foreign key '{9F6178FD-4B30-4727-BA95-0FED975D4D91}' has a name that might cause problems for the Access application to function correctly against SQL Server.
A2SS0030 Identifier name might cause problems A2SS0030: Index '{9F6178FD-4B30-4727-BA95-0FED975D4D91}' has a name that might cause problems for the Access application to function correctly against SQL Server.
A2SS0030 Identifier name might cause problems A2SS0030: Foreign key '{E4FC6A8B-64F9-4E78-8B90-445F2B9E44B1}' has a name that might cause problems for the Access application to function correctly against SQL Server.
A2SS0030 Identifier name might cause problems A2SS0030: Index '{E4FC6A8B-64F9-4E78-8B90-445F2B9E44B1}' has a name that might cause problems for the Access application to function correctly against SQL Server.

It would sure be great if Microsoft would include in messages such as these the table name and identifier/column name.

Bob

Answer 1

I have written it off to database corruption. I will proceed to use SSMA to convert to sql server and then remove the 15 or so erroneous indexes.

Bob

Answer 2

On UtterAccess.com I posted a link to this thread since I had only gotten one reply. One of the guys asked if I cooulde supply a sample to look. I was creating it and realized that it would have to be empty. SO I created a new MDB and imported 3 tables known to cause problems and them removed the data. I ran SSMA and had no warnings in stage one of the conversion. It seems it must have something to do with the data.

I took over support of this database about three years ago so I do not know how it was managed before I took it over.

I think I will now look at data issues, like primary keys or indexed fields that have blank or null fields or duplicates.

Bob

Answer 3

After extensive testing, it appears that the issue is table corruption. the only thing that worked was to copy the column definitions to a new table. I ran that with ssma and had no errors (no data).

Bob

Answer 4

It would be very interesting if someone from Microsoft could advise how to interpret the error messages.

Bob

Answer 5

Mike. thanks. I sent an email to the azcommunity.

Also I was never able to locate " dma.exe.config or dmacmd.exe.config".

Albert Kallal, an Access MVP said he has never seen these errors.

Also the errors refer to the GUID, which I think is different from the original GUID shown in the Access info. I I could never tie it to a Primary Key or Index.

Bob