You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File "D:\home\python364x64\lib\site-packages\azure\storage\table\tableservice.py", line 1096, in _perform_request
return super(TableService, self)._perform_request(request, parser, parser_args, operation_context)
File "D:\home\python364x64\lib\site-packages\azure\storage\storageclient.py", line 280, in _perform_request
raise ex
File "D:\home\python364x64\lib\site-packages\azure\storage\storageclient.py", line 248, in _perform_request
raise ex
File "D:\home\python364x64\lib\site-packages\azure\storage\storageclient.py", line 235, in _perform_request
_http_error_handler(HTTPError(response.status, response.message, response.headers, response.body))
File "D:\home\python364x64\lib\site-packages\azure\storage_error.py", line 114, in _http_error_handler
raise AzureHttpError(message, http_error.status)
azure.common.AzureMissingResourceHttpError: Not Found
{"odata.error":{"code":"TableNotFound","message":{"lang":"en-US","value":"The table specified does not exist.\nRequestId:87821d3e-a002-0030-37d4-0f46c2000000\nTime:2019-05-21T12:52:29.5613381Z"}}}
This resulted as soon as the deployment finished successfully - not errors at any of the steps.
The demo did not work, we saw the webapp but the simulated devices were not producing any data and therefore the ML part did not get a chance of producing results.
The text was updated successfully, but these errors were encountered:
silviews
changed the title
Data generator error from the device: TableNotFound
Data generator error from device: TableNotFound
May 29, 2019
I had a similar error when trying to view the device logs in the webapp. Of particular interest is the following line (which was not in the original post, perhaps because it was cut out):
File "D:\home\site\wwwroot\flask\app.py", line 161, in get_device_logs log_entities = table_service.query_entities('logs', filter=query_filter)
Indeed, the logs table does not exist in the Table Storage. If I create the table manually, the error disappears and the device view shows a graph which was not there before I created the table. But the graph does not show any data because there are other errors in the data generation scripts.
The logs table should be created by the Simulator WebJob:
File "D:\home\python364x64\lib\site-packages\azure\storage\table\tableservice.py", line 1096, in _perform_request
return super(TableService, self)._perform_request(request, parser, parser_args, operation_context)
File "D:\home\python364x64\lib\site-packages\azure\storage\storageclient.py", line 280, in _perform_request
raise ex
File "D:\home\python364x64\lib\site-packages\azure\storage\storageclient.py", line 248, in _perform_request
raise ex
File "D:\home\python364x64\lib\site-packages\azure\storage\storageclient.py", line 235, in _perform_request
_http_error_handler(HTTPError(response.status, response.message, response.headers, response.body))
File "D:\home\python364x64\lib\site-packages\azure\storage_error.py", line 114, in _http_error_handler
raise AzureHttpError(message, http_error.status)
azure.common.AzureMissingResourceHttpError: Not Found
{"odata.error":{"code":"TableNotFound","message":{"lang":"en-US","value":"The table specified does not exist.\nRequestId:87821d3e-a002-0030-37d4-0f46c2000000\nTime:2019-05-21T12:52:29.5613381Z"}}}
This resulted as soon as the deployment finished successfully - not errors at any of the steps.
The demo did not work, we saw the webapp but the simulated devices were not producing any data and therefore the ML part did not get a chance of producing results.
The text was updated successfully, but these errors were encountered: