Message337760
Since I just dug enough to find it, the best way to diagnose problems with dependent DLLs not being found is probably to run Process Monitor [1] while doing the import and checking its logs. It should show the paths that were attempted to be accessed.
[1]: http://technet.microsoft.com/en-us/sysinternals/bb896645 |
|
Date |
User |
Action |
Args |
2019-03-12 15:45:21 | steve.dower | set | recipients:
+ steve.dower, brett.cannon, paul.moore, ncoghlan, tim.golden, jkloth, lukasz.langa, eric.snow, zach.ware, mattip, eryksun |
2019-03-12 15:45:21 | steve.dower | set | messageid: <1552405521.1.0.0491360072525.issue36085@roundup.psfhosted.org> |
2019-03-12 15:45:21 | steve.dower | link | issue36085 messages |
2019-03-12 15:45:21 | steve.dower | create | |
|