Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
IgorHi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>
Showing posts with label client. Show all posts
Showing posts with label client. Show all posts
Tuesday, March 27, 2012
Connecting to SQL Server 2005
Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
Igor
Hi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>
|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David
|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>
|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
Igor
Hi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>
|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David
|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>
|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>
Connecting to SQL Server 2005
Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
IgorHi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
>>
>> This is not quite right. MDAC is part of the operating system, but SQL
>> Native Client is not.
>>
>> The SQL Native Client is a seperate install. It is included in the SQL
>> Server distribution and available here:
>> http://msdn.microsoft.com/data/sqlnative/default.aspx
>> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
>> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
>> (SQLNCLI). SQLNCLI is the best, but you must install it.
>> SQL Native Client also has a new ODBC driver.
>> David
>
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
IgorHi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
>>
>> This is not quite right. MDAC is part of the operating system, but SQL
>> Native Client is not.
>>
>> The SQL Native Client is a seperate install. It is included in the SQL
>> Server distribution and available here:
>> http://msdn.microsoft.com/data/sqlnative/default.aspx
>> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
>> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
>> (SQLNCLI). SQLNCLI is the best, but you must install it.
>> SQL Native Client also has a new ODBC driver.
>> David
>
Thursday, March 22, 2012
Connecting to SQL 2005 from a client pc
I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:
PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.
Thank you for any suggestions
Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.
ANY info you might have would be appreciated, thanks!
|||I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.
I hope someone could help us on this matter. (ASAP)
|||Couple of things about Report Builder -
1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.
2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.
When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.
Hope that helps,
-Lukasz
|||Hi Lukasz,I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.
Thoughts?|||
Have you had any luck with this issue? If so, please let me know what you did to figure it out.
|||Have you had any luck with this problem. If so please inform me on your solutions.|||Your users, are they able to see the report builder button in report manager?
What is the exact error they get when they try to launch report builder?
-Lukasz
|||Yes, they can see the button.When they click on the Report Builder button a dialog pops up saying that it is Launching Application.
This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."
When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."|||We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder?|||
I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:
http://msdn2.microsoft.com/en-us/library/ms156014.aspx
-Lukasz
|||Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?
-Lukasz
|||I had this same problem and found a good solution here.|||I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.
Any ideas how to fix this problem when running Reporting Services in integrated mode?
Connecting to SQL 2005 from a client pc
I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:
PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.
Thank you for any suggestions
Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.
ANY info you might have would be appreciated, thanks!
|||I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.
I hope someone could help us on this matter. (ASAP)
|||Couple of things about Report Builder -
1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.
2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.
When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.
Hope that helps,
-Lukasz
|||Hi Lukasz,I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.
Thoughts?|||
Have you had any luck with this issue? If so, please let me know what you did to figure it out.
|||Have you had any luck with this problem. If so please inform me on your solutions.|||Your users, are they able to see the report builder button in report manager?
What is the exact error they get when they try to launch report builder?
-Lukasz
|||Yes, they can see the button.When they click on the Report Builder button a dialog pops up saying that it is Launching Application.
This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."
When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."|||We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder?|||
I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:
http://msdn2.microsoft.com/en-us/library/ms156014.aspx
-Lukasz
|||Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?
-Lukasz
|||I had this same problem and found a good solution here.|||I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.Any ideas how to fix this problem when running Reporting Services in integrated mode?
Connecting to SQL 2005 from a client pc
I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:
PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.
Thank you for any suggestions
Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.
ANY info you might have would be appreciated, thanks!
|||I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.
I hope someone could help us on this matter. (ASAP)
|||Couple of things about Report Builder -
1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.
2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.
When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.
Hope that helps,
-Lukasz
|||Hi Lukasz,I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.
Thoughts?|||
Have you had any luck with this issue? If so, please let me know what you did to figure it out.
|||Have you had any luck with this problem. If so please inform me on your solutions.|||Your users, are they able to see the report builder button in report manager?
What is the exact error they get when they try to launch report builder?
-Lukasz
|||Yes, they can see the button.When they click on the Report Builder button a dialog pops up saying that it is Launching Application.
This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."
When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."|||We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder?|||
I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:
http://msdn2.microsoft.com/en-us/library/ms156014.aspx
-Lukasz
|||Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?
-Lukasz
|||I had this same problem and found a good solution here.|||I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.Any ideas how to fix this problem when running Reporting Services in integrated mode?
sqlsql
Connecting to SQL 2005 from a client pc
I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:
PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.
Thank you for any suggestions
Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.
ANY info you might have would be appreciated, thanks!
|||I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.
I hope someone could help us on this matter. (ASAP)
|||Couple of things about Report Builder -
1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.
2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.
When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.
Hope that helps,
-Lukasz
|||Hi Lukasz,I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.
Thoughts?|||
Have you had any luck with this issue? If so, please let me know what you did to figure it out.
|||Have you had any luck with this problem. If so please inform me on your solutions.|||Your users, are they able to see the report builder button in report manager?
What is the exact error they get when they try to launch report builder?
-Lukasz
|||Yes, they can see the button.When they click on the Report Builder button a dialog pops up saying that it is Launching Application.
This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."
When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."|||We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder?|||
I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:
http://msdn2.microsoft.com/en-us/library/ms156014.aspx
-Lukasz
|||Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?
-Lukasz
|||I had this same problem and found a good solution here.|||I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.Any ideas how to fix this problem when running Reporting Services in integrated mode?
connecting to remote server
Hi friends
we've C# app that connects a sql server 2005. we've new requests from client that when users go offsite they still want use our app and connect to sql server.
my question is how can we connect to sql server remotely ?
is it using TCP/IP protocol ? if so how do we do that ?
Thanks for ur help.
wonderful mate. thank you very much for those links.
am looking something like that.will go thru those articles.
Thanks again.
we've C# app that connects a sql server 2005. we've new requests from client that when users go offsite they still want use our app and connect to sql server.
my question is how can we connect to sql server remotely ?
is it using TCP/IP protocol ? if so how do we do that ?
Thanks for ur help.
Use SQL Server Configuration Manager, select protocols for your instance. On the right side, enable TCP protocol. You need restart the sql server. If you have firewall, don't forget to put your tcp port into exception, (also UDP port 1434 for sql browser if you have a named instance.)
|||Thanks for that Hong.
i've one more question on this.
what should my connection string contain ? should it contain IP address for server name ?
Thanks again|||btw we use patterns and practices library for our database connections.|||Either IP address or server name should work if your DNS works correctly.
Thanks.|||
Thank you very much for ur replies Hong.
still need some clarification as am not fully aware how DNS works .
currently in our connections string we specify our sql server name as "mallu" and other info like database etc.,(btw we use enterprise library for data access)
are you saying that once we open port on our server and allow remote connects abv connection string just works ? i mean say if we our server is in new zealand and user goes to say australia and he still be able connect ?
Thanks for clarification .
much appreciated you can point me to some resource on these issues on net
|||Hi prk,
DNS is the Domain Name System -- essentially the directory service that translates your hostnames into IP address. Your network probably has one and your network admin should be able to give you more info.
Regardless of the geography, if your server is configured to listen to a remote protocol and the firewall (if any) is configured properly, you should be able to connect from your client app. The BOL contains some great information on how to do so:
http://msdn2.microsoft.com/en-us/library/ms190608.aspx
http://msdn2.microsoft.com/en-us/library/ms187853.aspx
Also, check out this tutorial on connecting to the database:
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
Il-Sung.
|||Il-Sungwonderful mate. thank you very much for those links.
am looking something like that.will go thru those articles.
Thanks again.
Monday, March 19, 2012
Connecting to MSDE via client
Hope someone can explain why this happened.
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============
Connecting to MSDE from client
We are using MSDE as a cheap datastore in our client/server app. MSDE is installed only on the server and both the server and the clients connect to it from their machines.
When we deploy on Windows XP, we see that our code running on the server can access MSDE, but our code running on a client machine cannot connect to MSDE.
The clients are able to connect on Windows 2000 ... can anyone help me understand this ?
Thanks in advance,
ethan
MSDE only allow local access.Connecting to MDF file over Workgroup
Hi
I've build a client management (Windows) application in VS2005 which works fine on the local development machine but falls over when trying to connect to the SQL Server Express file located on a second machine on the same Workgroup. Several of the apllications will connect to the database file from networked computers.
The error I get when testing the connection or trying to connect via the App is:
-------------------
The file "Z:\BushBreaks.MDF" is on a network path that is not supported for database files.
An attempt to attach and auto-named database for file z:\bushbreaks.mdf failed. A database with the same name exists, or specified file cannot be opened or it is on a UNC share.
-------------------
How can I configure this database and/or connection to be able to allow connections to the MDF file? Please note that security is not an issue if that is at all relevant.
Many Thanks
John
Current you can't use remote database file in your SQL connection. Here is a instruction about AttachDBFileName property in connection string from MSDN:
The name of the primary database file, including the full path name of an attachable database. The path may be absolute or relative by using the DataDirectory substitution string. If DataDirectory is used, the database file must exist within a subdirectory of the directory pointed to by the substitution string.
Remote server, HTTP, and UNC path names are not supported.
For more information, you can refer to:
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx
Connecting to local instance with firewall client enabled
I'm running SQL Server 2000 SP3 on my XP Pro laptop and everything
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris BettertonIf you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris BettertonIf you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Connecting to local instance with firewall client enabled
I'm running SQL Server 2000 SP3 on my XP Pro laptop and everything
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris Betterton
If you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris Betterton
If you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Sunday, March 11, 2012
Connecting to AS 400
Hi,
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
Connecting to AS 400
Hi,
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.
Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.
Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
Thursday, March 8, 2012
Connecting to Analysis Server 2005
Does anybody knows if a 2000 analysis services client could connect to a 2005 Analysis Server ?
Thanks
If by "client" you mean "client components", i.e. PTS aka OLEDB driver msolap80.dll - then the answer is NO. There was a version of ADOMD.NET which shipped after AS2000 but before AS2005 - it can connect to AS2005.
HTH,
Mosha (http://www.mosha.com/msolap)
Connecting to Analysis Server 2005
Does anybody knows if a 2000 analysis services client could connect to a 2005 Analysis Server ?
Thanks
If by "client" you mean "client components", i.e. PTS aka OLEDB driver msolap80.dll - then the answer is NO. There was a version of ADOMD.NET which shipped after AS2000 but before AS2005 - it can connect to AS2005.
HTH,
Mosha (http://www.mosha.com/msolap)
Connecting to an alias fails
Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
Connecting to an alias fails
Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
Wednesday, March 7, 2012
Connecting to a Network Server - a simple question !!
Hi
My question should be relatively simple.
I have a server machine (Windows XP + SQL SERVER 2005 EXPRESS) : IP (192.168.1.1)
2 client machines:
Client 1 (Windows XP + SQL SERVER 2005 EXPRESS) : IP (192.168.1.100)
Client 2 (Windows XP + SQL SERVER 2005 EXPRESS) : IP (192.168.1.101)
I want to connect the 2 clients to the server database in a simple client\server arch.
what should I do ?!!!
Thank you in advance.
By default SQL EXPRESS does not allow remote connections and is meant to be used as a Client database only.
You can enable the Remote Connections with configuration tools, but there are limitations.
I am not sure what you mean in a Client Server architecture, as you are using all Client OS versions, and connecting SQL - SQL would not necessarily be a Client Server arch.
More info would help as to what you are trying to accomplish in setting up 3 instances of SQL Server to talk to each other (other than replication, etc).
Ben Miller
|||
developer00x wrote:
Hi
My question should be relatively simple.
I have a server machine (Windows XP + SQL SERVER 2005 EXPRESS) : IP (192.168.1.1)
2 client machines:
Client 1 (Windows XP + SQL SERVER 2005 EXPRESS) : IP (192.168.1.100)
Client 2 (Windows XP + SQL SERVER 2005 EXPRESS) : IP (192.168.1.101)
I want to connect the 2 clients to the server database in a simple client\server arch.
what should I do ?!!!
Thank you in advance.
Hi Developer00x,
You will need a minimum install of sql server 2005 standard edition to achieve what you are attempting to do...
Barry Andrew|||I am not sure, why he should need a Std. Edition for the scenario described as he did not mention anything about replication or something else. If he just wants to connect to the server from the clients, he will just need to have any SNAC / OLEDB / MDAC (which is shipped with Windows XP) and enable remote connections like Ben suggested.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Problem solved ..
Thank you,
Subscribe to:
Posts (Atom)