>I voted. BTW, did you check the other bug I posted? It seems to be the exact same problem and they have a few workarounds. May be you can try one of them.

When I installed those servers, I spent a lot of times trying to figure out the best way to do this. It is only when I installed an old version of the SQL Server components (the 2008 version), that everything started to work. It was weird because I was hitting a SQL Server 2012. But, then again, I thought it might make sense because I was running in SQL Server 2008 emulation mode. So, I left it at there since then.

But, it is only this week when I tried to remove the SQL Server 2008 emulation mode and use SQL Server 2012 as is that I found out that this reader type error came back. Because, the goal was to get rid of the 2008 SMO and CLR Types files. So, when removed, the error came back.

But, I see something new. There is a way to specify something in the connection string. I will have to see about it. All those are attempts I already tried last year. So, I will see about the connection string.

But, all those workarounds since to indicate that there is in fact something that should be addressed. I will see what they have to say on my post.