Database vendor code: 17 appears when previewing or printing reports from Citrix Server. Same report on application server works just fine

I'm upgrading from 2015 SQL to 2020 PU3 SQL.

The migration and conversion has been successful, but I can't go live tomorrow, unless I resolve their printing problem on their Citrix Server. That's where all users connect and work. I started the go live Friday afternoon and have work Saturday and today and would hate to lose another weekend to this project. 

I've reviewed the Sage KB's on Vendor Code 17, and they all seem to point to an invalid MAS_Reports password, Incorrectly named SQL instance, SQL port being blocked and TCP/IP not being enabled. I"ve checked all these settings and they're all good. 

Any suggestions?

John Kerr

Parents
  • I had this happen and it turned out the Test Connection button worked, but the path in the SQL Settings utility was using [local], instead of the actual server name. It sounds like this might not apply to your situation, as your Citrix server is unlikely to also be your SQL server - but I just wanted to throw this out there. I guess this falls under the "Incorrectly named SQL instance" cause.

  • in reply to rclowe

    Morning Cullen

    I checked the instance name when running the utility and it was correct, well it was actually the fully qualified domain name of the SQL server. 

  • in reply to Johnbhoy

    Figured as much. Checked all the protocols? Named Pipes and everything?

Reply Children