February 18, 201511 yr Just a note for anyone who has just installed Tileproxy and cannot get it to work. There are many threads on the internet discussing this error message: "proxy user: ERROR connecting to filter port: 0x80070002" Almost all of them say that the problem is due to a Windows conflict involving Tileproxy drivers not being properly authorized, and the typical suggestions for resolving the conflict involve various ways of disabling Windows' checking of whether the Tileproxy drivers are signed (for example, by installing and running a program called Driver Signature Enforcement Overrider 1.3b). In my case, the error had nothing to do with Tileproxy driver signatures. I was trying to set up the Tileproxy data files on a ramdisk. I used the ramdisk software's default settings when creating the ramdisk, which set the files cluster size at 4kb. As I subsequently discovered, 4kb is too small for Tileproxy files, so that choice kept Tileproxy from working. When I changed to a cluster size of 16kb, I stopped getting the "proxy user: ERROR connecting to filter port: 0x80070002" message. So, don't assume that if you are seeing a Tileproxy error connecting to filter port 0x80070002 message, it must be due to a problem with Windows' driver signatures, even if that is the most common cause of the error message. Vic
Create an account or sign in to comment