Question

Help with random errors when loading to Azure OGDI Open Data Catalogue

  • 10 September 2013
  • 0 replies
  • 1 view

Here are the errors I get when running FME to load our Azure hosted OGDI Open Data Catalogue – the errors seem to be random, the process will cometimes complete with no errors, but will also fail occasionally right after a successful load and vice versa..

 

What do you think I need to change?

 

 

 

Example Fail 1:

 

Microsoft Windows Azure OGDI Writer: Connecting to service 'banffdata'

 

Microsoft Windows Azure OGDI Writer: Directive 'WRITER_MODE' has the value 'INSERT'

 

Microsoft Windows Azure OGDI Writer: Dropping table 'BuildingPermits' ...

 

Microsoft Windows Azure OGDI Writer: Creating table 'BuildingPermits' ...

 

Python Exception <URLError>: <urlopen error There is a problem with the requested URL: [Errno 10054] An existing connection was forcibly closed by the remote host>

 

Microsoft Windows Azure OGDI Writer: Aborted writing table 'BuildingPermits'

 

MS Access Reader: Closing `Y:\\Environmental Services\\_Planning\\Access Permit Ledger\\Permit_Ledger.accdb' . Read operation complete

 

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

 

FME Session Duration: 30.6 seconds. (CPU: 0.3s user, 0.3s system)

 

END - ProcessID: 4580, peak process memory usage: 46892 kB, current process memory usage: 46424 kB

 

 

 

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

 

Program Terminating

 

 

 

Translation FAILED.

 

 

 

Tried rerunning the same workspace again within seconds and got this error….

 

Example Fail 2:

 

Microsoft Windows Azure OGDI Writer: Missing value for ogdi_entitykind. Defaulting to 'BuildingPermits item'

 

Microsoft Windows Azure OGDI Writer: Missing value for ogdi_expireddate. Defaulting to '2100-01-01'

 

Microsoft Windows Azure OGDI Writer: Directive 'SERVICE_NAME' has the value 'banffdata'

 

Microsoft Windows Azure OGDI Writer: Directive 'TABLE_NAME' has the value 'BuildingPermits'

 

Microsoft Windows Azure OGDI Writer: Directive 'CREATE_TABLE' has the value 'Yes'

 

Microsoft Windows Azure OGDI Writer: Directive 'DROP_TABLE' has the value 'Yes'

 

Microsoft Windows Azure OGDI Writer: Connecting to service 'banffdata'

 

Python Exception <AttributeError>: 'URLError' object has no attribute 'read'

 

Microsoft Windows Azure OGDI Writer: Aborted writing table 'BuildingPermits'

 

MS Access Reader: Closing `Y:\\Environmental Services\\_Planning\\Access Permit Ledger\\Permit_Ledger.accdb' . Read operation complete

 

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

 

FME Session Duration: 21.8 seconds. (CPU: 0.3s user, 0.2s system)

 

END - ProcessID: 4796, peak process memory usage: 44212 kB, current process memory usage: 43628 kB

 

 

 

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

 

Program Terminating

 

 

 

Translation FAILED.

 

 

 

Reran the same workspace right after this 2nd fail – and success!>?

 

Features Written Summary

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

BuildingPermits (BuildingPermits)                                         1672

 

==============================================================================

 

Total Features Written                                                    1672

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

MS Access Reader: Closing `Y:\\Environmental Services\\_Planning\\Access Permit Ledger\\Permit_Ledger.accdb' . Read operation complete

 

Translation was SUCCESSFUL with 5 warning(s) (1672 feature(s) output)

 

FME Session Duration: 3 minutes 12.1 seconds. (CPU: 1.6s user, 0.2s system)

 

END - ProcessID: 2480, peak process memory usage: 53352 kB, current process memory usage: 52968 kB

 

Translation was SUCCESSFUL

 

 

 

SUMMARY and NOTE

 

I also reran the workspace after the successful load, and got the 1st error listed above, I reran the workspace again, and this time I didn’t get the 2nd error listed above, I got a successful load.

 

So are these issues with my Azure account/setup?  Any suggestions on what needs to be fixed with regards to the errors I’m getting?

 

I had months of successful continuous daily updates, only in the past few weeks have I been getting these errors – though I haven’t changed anything on the Azure end.

 

Thank you for any suggestions.

 

Steve

 


0 replies

Be the first to reply!

Reply