Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts

Sunday, March 25, 2012

Cannot print landscape

In Report Manager in SSRS 2005, no matter what printer I go to, there is no landscape option. It's not the driver, unless the driver for the printer isn't like SSRS because I can print landscape on any of these pritnters in any other application. Why is that? I do not see an option to switch to landscape period after looking at my printer properties afer clicking the print button from SSRS

From what I understand it is not the printer you have to choose to be landscape but the report before you print it.

Set the report width and height to be the opposite to what they are now. E.g. US letter set width to 11 and height to 8.5

Craig

Tuesday, March 20, 2012

Cannot open database requested in login 'northwind'. Login fails.

I work for DataDirect-Technologies. My customer is using our Connect for ODBC
5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
tries to connect using a simple C application he gets the error
"[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
requested in login 'northwind'. Login fails." The customer has tried using
the IP Address and the machine name. He has tried connecting to Northwind and
Master. He is using the sa login with a password. He is able to connect with
the same information from a Windows machine either using Windows
Authentication or SQL Server authentication.
There must be some setting within his SQL Server database that does not
allow remote connections, is anyone aware of something like this?
Actually, to update the issue: the customer can connect from a remote Windows
client to his SQL Server 7 database using the MS ODBC driver. However, if he
takes that same data source on his remote Windows client and changes the
connection info to point to the machine name and port number of the Solaris
box where a TCP/IP packet sniffer
(ftp://ftp.datadirect.com/download/da...ools/snoop.jar) is running and
the packet sniffer re-routes the connection to the SQL Server database, he
sees the same error that he gets with the DataDirect ODBC driver on Solaris.
So it appears that SQL Server must be configured only to disallow connections
coming from that Solaris machine, not necessarily all remote connections.
Does anyone know what setting is controlling this?
"Pat Frost" wrote:

> I work for DataDirect-Technologies. My customer is using our Connect for ODBC
> 5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
> tries to connect using a simple C application he gets the error
> "[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
> requested in login 'northwind'. Login fails." The customer has tried using
> the IP Address and the machine name. He has tried connecting to Northwind and
> Master. He is using the sa login with a password. He is able to connect with
> the same information from a Windows machine either using Windows
> Authentication or SQL Server authentication.
> There must be some setting within his SQL Server database that does not
> allow remote connections, is anyone aware of something like this?

Cannot open database requested in login 'northwind'. Login fails.

I work for DataDirect-Technologies. My customer is using our Connect for ODB
C
5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When h
e
tries to connect using a simple C application he gets the error
"[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open dat
abase
requested in login 'northwind'. Login fails." The customer has tried using
the IP Address and the machine name. He has tried connecting to Northwind an
d
Master. He is using the sa login with a password. He is able to connect with
the same information from a Windows machine either using Windows
Authentication or SQL Server authentication.
There must be some setting within his SQL Server database that does not
allow remote connections, is anyone aware of something like this?Actually, to update the issue: the customer can connect from a remote Window
s
client to his SQL Server 7 database using the MS ODBC driver. However, if he
takes that same data source on his remote Windows client and changes the
connection info to point to the machine name and port number of the Solaris
box where a TCP/IP packet sniffer
(ftp://ftp.datadirect.com/download/d...tools/snoop.jar) is running an
d
the packet sniffer re-routes the connection to the SQL Server database, he
sees the same error that he gets with the DataDirect ODBC driver on Solaris.
So it appears that SQL Server must be configured only to disallow connection
s
coming from that Solaris machine, not necessarily all remote connections.
Does anyone know what setting is controlling this?
"Pat Frost" wrote:

> I work for DataDirect-Technologies. My customer is using our Connect for O
DBC
> 5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When
he
> tries to connect using a simple C application he gets the error
> "[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open d
atabase
> requested in login 'northwind'. Login fails." The customer has tried using
> the IP Address and the machine name. He has tried connecting to Northwind
and
> Master. He is using the sa login with a password. He is able to connect wi
th
> the same information from a Windows machine either using Windows
> Authentication or SQL Server authentication.
> There must be some setting within his SQL Server database that does not
> allow remote connections, is anyone aware of something like this?

Friday, February 10, 2012

Cannot find the driver for JDBC

Hi all, I am building a program using Java and SQL express and I need the driver in order to connect to the database. I have downloaded I think a version for sql server 2005 but it did not work. Can somebody tell me if such driver exists?

Thank you all

Adam:

Yes, such a driver exists and can be downloaded here:

http://msdn.microsoft.com/data/jdbc/

If you have any issues please let us know.

-shelby

Shelby Goerlitz

Microsoft SQL Server Data Programmability