{.NET + SQL_Server + Azure + devLeadership + technology}

Menu

Monthly Archives: May 2009

Connection can not be established. Server name, port number, or credentials may be invalid.

I just got that message when trying to enter a perfectly valid set of connection/credential info into an SSIS package. But testing the connection failed.

Turns out my issue, and maybe your issue too, is that SSIS doesn’t remove white space from the server name textbox. So if you pasted in the name of the FTP server, as I did, you might have fallen victim to the “trailing space” that is frequently copied with your text, and instead of trying to connect to “ftp.com” it tried to connect to “ftp.com ” notice the extra space.

Either this never worked in the first place as I wanted, or MS has changed how they are doing things in SSRS 2008.

I now don’t see any of the errors in the tables I had been looking in, and in fact, the errors don’t show up in any of their logs either. This is crap.

If you are like me, you don’t like the fact that the first time you realize that a data driven subscriptions in SQL Server Reporting Services has been failing is when someone comes up to you and says “Hey, I did XYZ and I never saw the server kick off an email.”

Really? Let me check…. oh, looks like it has been broken for god knows how long. What the heck?

Well, I wrote a script to notify you when there are errors on the report server.

First, you need to setup Database Mail. Expand Management, and pick Database Mail. For my script I used the name “Email Profile” for the “Email Profile” get it?