ADO.NET python error since Windows update 1903

[pstueven]

Hi,

since I updated my Windows 10 with the 1903 Update, my PowerBI Desktop python connection does not work anymore. It says:

Details: "ADO.NET: Þγτĥòʼn ѕçяìφť ęяŕõř.
Traceback (most recent call last):
File "PythonScriptWrapper.PY", line 63, in <module>
for key in dir():
TypeError: 'str' object is not callable
"

None of the mentioned code is in my code and I do not know where to find the PythonScriptWrapper to try to debug it.

When I execute the python code in a shell, it works just fine with the same python installation. I tested it with Python 3.5 and 3.7, while 3.5 was installed before the update.

I would appreciate any help

Best regards

Solution:

https://community.powerbi.com/t5/Issues/ADO-NET-python-error-since-Windows-update-1903/idc-p/765835/...

[v-qiuyu-msft]

Hi @pstueven, 

Please share the pbix file with us. Do remove sensitive data in the report, upload pbix file to your OneDrive, paste the share link here. 

Best Regards,
Qiuyun Yu

[pstueven]

Hey @v-qiuyu-msft ,

thanks for your quick response! Unfortunately I am not allowed to share OneDrive links in my organisation. So I had to use Google Drive.

I could not anonymize my data, so I share the script, some data and a short readme file. You will need an FTP to test.

https://drive.google.com/open?id=1219Ru0hpiENN73xopPpeRNUoYzFs4gCw

Thanks for your help so far!

@pstueven 

[v-qiuyu-msft]

Hi @pstueven, 

I don't have FTP server environment to test it on my side. For your issue, please create a support ticket to let engineers look into the issue on your side. 

Best Regards,
Qiuyun Yu

[otarb]

Hi @pstueven 

Workaround: Please rafrain from using variable called 'dir' in the script.

Currently there in issue with execution when script has variable called 'dir'. We are working to resolve this. In the meantime please use different variable name.

Thanks,
Otar

[pstueven]

Thanks @otarb ! Despite I already had a workaround, renaming the variable is a much better solution as the workaround was not a python best practice. In fact I renamed the variable in my workaround because I changed it from a directory string to an index, which also resolved the issue.

I committed your solution to the support team at Microsoft dealing with my ticket! 🙂

Best regards