Year 30828 out of range

[jinder]

Hi,

I've used pyinstaller to build px on Windows 7, using Python 3.6, I'm getting the following error while trying to connect to the proxy: ValueError year 3083 is out of range in sspi.py line 111.

Any ideas?

[jinder]

Looks like it might be caused by this: https://sourceforge.net/p/pywin32/bugs/748/

Will try downgrading to Python 3.5

[jinder]

Have confirmed that it's the bug linked above. Downgrading to Python 3.5 has fixed my issue, so will close.

[ghost]

Shouldn't we keep this open until it's fixed upstream?

[stolpovsky]

@jinder Please consider changing to 'open' until fixed.

[jinder]

Reopened

[genotrance]

Looks like this could be fixed if Px switches to winkerberos, per the link to the pywin32 issue. I'm not sure if it's worth the effort but open to suggestions.

[snovik75]

I confirm the issue. Is there another workaround apart from downgrading python?

[genotrance]

Just for kicks, I tried this with Python 3.6.1 and 3.6.2. I tried with pywin32 v220 as well as v221 and it's still broken. The fix is required within win32security.pyd which is C code and not easy to work around.

[genotrance]

Thanks to help from the winkerberos team, Px works with winkerberos so Python 3.6+ is now supported.

pywin32 SSPI is still supported so if winkerberos isn't available, Px will fall back to pywin32 as long as the Python version is < 3.6.

[genotrance]

Given Px now works around this issue by using winkerberos, I propose marking this as fixed. Feedback appreciated.

[genotrance]

So I had to bring back pywin32 for NTLM auth since winkerberos was failing for some NTLM use cases. Some folks may still run into this issue. The recommendation is to upgrade your Python to the latest version since a fix is in place.

[lvfanqie]

@genotrance I still got this issue with latest px code. My python is 36-64. How could i fix it?

[genotrance]

Is it possible to update your Python to latest version somehow? Also install latest version of pywin32?

[genotrance]

I know it is broken on 3.6.1 and 3.6.2. I haven't tried 3.6.3 but I'm currently running 3.6.4 and don't see the issue anymore.

[lvfanqie]

I checked my python version , it's 3.6.6. Is there any way to fix it?

[lvfanqie]

I found this issue happens more when there's multi clients connected through proxy.

[genotrance]

What version of pywin32 do you have installed? I have 222. Also is your Python 32-bit or 64-bit? Miniconda or Python.org?

[lvfanqie]

pywin32=223, python is 3.6.6-64 bit from python.org

[lvfanqie]

@genotrance any suggestion?

[genotrance]

@lvfanqie: can you check if this issue helps? Looks like older version of 220 was also present in the path.

[lvfanqie]

@genotrance my win32api version is '223'. How could I check pywintype version? I got following errors:

import pywintypes
fixed_file_info = win32api.GetFileVersionInfo(pywintypes.file, '\')
Traceback (most recent call last):
File "", line 1, in
pywintypes.error: (1813, 'GetFileVersionInfo:GetFileVersionInfoSize', 'The specified resource type cannot be found in the image file.')

[genotrance]

I tried and no idea :(

Another option is to pip remove pywin32 and then reinstall and see if it helps any. I don't have a 64-bit Python setup so unsure if this is broken or an install issue.

[lvfanqie]

unfortunately, I tried reinstall the pywin32 but still get the same issue.