Can't create new datasource

I installed analysis services this last week and now when I try to add a new
data source in reporting services I get an error that says The OLE DB
provider SQLOLEDB has not been installed or is not valid. Do you wan tto
reset the connect string? It has a cancel and an OK button but no matter
which one you push it does nothing. It was working before I did the install
and when I did the install I just took the defaults and loaded up the latest
service pack. Any suggestions?
Thanks,
MelissaMy guess is that MDAC is messed up. One thing you might try is re-installing
the service pack for SQL Server. Either that or try re-installing the
appropriate version of MDAC.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Melissa" <Melissa@.discussions.microsoft.com> wrote in message
news:70F08879-5220-4681-9E31-852F7D542D4D@.microsoft.com...
> I installed analysis services this last week and now when I try to add a
new
> data source in reporting services I get an error that says The OLE DB
> provider SQLOLEDB has not been installed or is not valid. Do you wan tto
> reset the connect string? It has a cancel and an OK button but no matter
> which one you push it does nothing. It was working before I did the
install
> and when I did the install I just took the defaults and loaded up the
latest
> service pack. Any suggestions?
> Thanks,
> Melissa

Can't connect to through OLE DB to remote host - Database 'XXX' does not exist.

My application is to get some data from SQL/OLAP server.
When I try to open OleDbConnection using connection string:
"Provider=MSOLAP;Data Source=servername;Initial Catalog=dbname;"
I get message:
Database 'XXX' does not exist.
I can easily connect in the same way to localhost.
My user is olap administrator on the remote and localhost.
Using Analysis Manager or MDX Sample App from my PC I can connect to
both - local and remote DB.
The problem is I think that I still log in as anonymous user - I found
it in remote server's event log.
How can I log on authenticated? Analysis Manager can!
Any suggestions welcome!It seems that only I have that kind of problem.
Is there something I'm doing wrong?
Is it possible that my pc has to be in a domain? What if there is no
domain?
Guys please suggest me some checks or tests. Ask me something :)
This is my first approach to OLAP.
I don't know what to do.
On 27 Sie, 18:02, panko <PKoper...@.gmail.com> wrote:
> My application is to get some data from SQL/OLAP server.
> When I try to open OleDbConnection using connection string:
> "Provider=MSOLAP;Data Source=servername;Initial Catalog=dbname;"
> I get message:
> Database 'XXX' does not exist.
> I can easily connect in the same way to localhost.
> My user is olap administrator on the remote and localhost.
> Using Analysis Manager or MDX Sample App from my PC I can connect to
> both - local and remote DB.
> The problem is I think that I still log in as anonymous user - I found
> it in remote server's event log.
> How can I log on authenticated? Analysis Manager can!
> Any suggestions welcome!|||You all miserable geeks! ;)
I finally solved the problem.
The application was running as service. This service by default was
using System Local Account to log on. Therefore was refused by the
remote machine system which was not allowing this user to be
authenticated.
Solution was:
Services: MyService>Properties>Log On
Radio button on 'This Account': user and password that has right on
remote host.

cant connect to SQL2K running on W2K3SVR but can connect to SQL2K running W2KSVR with same

Hi,
I can't connect using an OLE DB connection string to SQL2K Server (SP3)
running on a Windows2003 Server, but using the same connection string (with
the address changed of course), I can connect to SQL2K Server (SP3) running
on Windows2000 Server.
I figure it must be a security issue on the W2K3 box. The logins and users
were created correctly with the correct passwords as I can connect to the
W2K3 box via Enterprise Manager just fine. The connection is set to TCP/IP
on port 1433 (default).
an example of my connection string (it is in a web application running on a
different server):
Application("dbconnstring") ="Provider=sqloledb;Data
Source=10.10.10.1;Network Library=DBMSSOCN;Initial Catalog=mydatabase;User
ID=mylogin;Password=mypassword;"
The only thing that changed is the IP address of the Win2003 server. I can
ping the server from either direction. I can scan port 1433 just fine with
a port scanner.
I am new to 2003 server, so I figure there must be a security setting
somewhere, but I haven't a clue where to look!
Any help would be appreciated!
TIA
Dave
.Hi Dave
> I can't connect using an OLE DB connection string to SQL2K Server (SP3)
> running on a Windows2003 Server, but using the same connection string
(with
> the address changed of course), I can connect to SQL2K Server (SP3)
running
> on Windows2000 Server.
> I figure it must be a security issue on the W2K3 box. The logins and
users
> were created correctly with the correct passwords as I can connect to the
> W2K3 box via Enterprise Manager just fine. The connection is set to
TCP/IP
> on port 1433 (default).
> an example of my connection string (it is in a web application running on
a
> different server):
> Application("dbconnstring") ="Provider=sqloledb;Data
> Source=10.10.10.1;Network Library=DBMSSOCN;Initial Catalog=mydatabase;User
> ID=mylogin;Password=mypassword;"
> The only thing that changed is the IP address of the Win2003 server. I
can
> ping the server from either direction. I can scan port 1433 just fine
with
> a port scanner.
> I am new to 2003 server, so I figure there must be a security setting
> somewhere, but I haven't a clue where to look!
>
Are you sure EM is connecting using TCP?
Can you connect locally using isql or isqlw to 127.0.0.1 ? (check that the
SQL Server client network utility on the server has TCP/IP as an enabled
protocol).
By port scanner, what do you mean? Are you scanning it on the server or from
outside the machine? Can you show that the server is listening on port 1433?
Check the SQL Server server network utility is listening on port 1433. Use
"netstat -a -n" (or "netsh interface ip show tcpconn") to look for an entry
like...
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
Try telnetting to the port, eg "telnet 127.0.0.1 1433". If it's listening on
port 1433 you should get a blank telnet screen. If it's not you'll get an
error like "Connecting To 127.0.0.1...Could not open a connection to host on
port 1434 : Connect failed"
Try the above from a remote machine to see if there's an issue with
connecting remotely.
Run the SQL Server Profiler and check the Security Audit->Audit Login, Audit
Login Failed, Audit Logout events.
Kind Regards, Howard|||Hi again,
I tried telnetting both on the server and remotely and I get the blank
screen. The problem is OLE-DB does not work on Win2003. I can connect my
.Net apps just fine though through the SQL connector and Enterprise Manager.
I enabled DTC on the Win2003 box to see if that would help (but it did not
help, as I figured) and rebooted.
Somehow, OLE-DB requests are being blocked by a security setting deep within
the bowels of Windows 2003.
I must not be alone on this problem as a staff of MCSEs & MCDBAs are
scratching their heads at the hosting company (name withheld)!
Whilest I wait for them to figure it out, where in SQL profiler is the
"security audit"?
Dave
"dammit Jim, I'm just a country programmer!"
--
"Howard Long" <howard@.howardlongxxx.com> wrote in message
news:camggl$gqh$1@.sparta.btinternet.com...
> Hi Dave
> > I can't connect using an OLE DB connection string to SQL2K Server (SP3)
> > running on a Windows2003 Server, but using the same connection string
> (with
> > the address changed of course), I can connect to SQL2K Server (SP3)
> running
> > on Windows2000 Server.
> >
> > I figure it must be a security issue on the W2K3 box. The logins and
> users
> > were created correctly with the correct passwords as I can connect to
the
> > W2K3 box via Enterprise Manager just fine. The connection is set to
> TCP/IP
> > on port 1433 (default).
> >
> > an example of my connection string (it is in a web application running
on
> a
> > different server):
> >
> > Application("dbconnstring") ="Provider=sqloledb;Data
> > Source=10.10.10.1;Network Library=DBMSSOCN;Initial
Catalog=mydatabase;User
> > ID=mylogin;Password=mypassword;"
> >
> > The only thing that changed is the IP address of the Win2003 server. I
> can
> > ping the server from either direction. I can scan port 1433 just fine
> with
> > a port scanner.
> > I am new to 2003 server, so I figure there must be a security setting
> > somewhere, but I haven't a clue where to look!
> >
> Are you sure EM is connecting using TCP?
> Can you connect locally using isql or isqlw to 127.0.0.1 ? (check that the
> SQL Server client network utility on the server has TCP/IP as an enabled
> protocol).
> By port scanner, what do you mean? Are you scanning it on the server or
from
> outside the machine? Can you show that the server is listening on port
1433?
> Check the SQL Server server network utility is listening on port 1433. Use
> "netstat -a -n" (or "netsh interface ip show tcpconn") to look for an
entry
> like...
> TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
> Try telnetting to the port, eg "telnet 127.0.0.1 1433". If it's listening
on
> port 1433 you should get a blank telnet screen. If it's not you'll get an
> error like "Connecting To 127.0.0.1...Could not open a connection to host
on
> port 1434 : Connect failed"
> Try the above from a remote machine to see if there's an issue with
> connecting remotely.
> Run the SQL Server Profiler and check the Security Audit->Audit Login,
Audit
> Login Failed, Audit Logout events.
> Kind Regards, Howard
>|||"Dave" <dave(delete_this)@.miraclecatDELETETHISTOO.com> wrote in message
news:%23NhiEGuUEHA.2356@.TK2MSFTNGP10.phx.gbl...
> Hi again,
> I tried telnetting both on the server and remotely and I get the blank
> screen. The problem is OLE-DB does not work on Win2003. I can connect my
> .Net apps just fine though through the SQL connector and Enterprise
Manager.
> I enabled DTC on the Win2003 box to see if that would help (but it did not
> help, as I figured) and rebooted.
> Somehow, OLE-DB requests are being blocked by a security setting deep
within
> the bowels of Windows 2003.
> I must not be alone on this problem as a staff of MCSEs & MCDBAs are
> scratching their heads at the hosting company (name withheld)!
> Whilest I wait for them to figure it out, where in SQL profiler is the
> "security audit"?
When Profiler has opened, File->New->Trace, enter your details. In the
Events tab, add the Security Audit /Audit Login & Audit Login failed. The
trace will help you identify the fault.
I was wondering if it is trying to use integrated security to connect. Try
setting up an AD account mylogin/mypassword on the W2K3 server and retrying.
Alternatively it could be the other way around, and you are using SQL Server
authentication, in which case you should check that the login exists in SQL
Server.
Any error messages?
Regards, Howard

Can't connect to linked SQL server: Cannot initialize the data source object of OLE DB provider

I find this most perplexing.

I have two servers, DEV and PROD. Now my DEV server works just great, I can connect to the linked server, query, etc... all is well.

So I'm setting up my PROD server and when I go to add the linked server I get:

Cannot initialize the data source object of OLE DB provider "SQLNCLI".... and Unable to complete login process due to delay in opening server connection.

Now I am running SQL Server 2005 and connecting to an SQL 2000 server.

The odd part is that this works just fine on DEV.

When I go to create the linked server I set:

Linked Server: "LinkedServerName"

Server Type: "SQL Server"

and that's it.

I go to Security and enter my DOMAIN\USER.ACCOUNT and then enter the login creds for the linked server.

When I click "OK" I get the above mentioned error code.

Any thoughts?

Please see if http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=990327&SiteID=1 could be useful for you.|||

Thanks, I'll check that out.

This whole thing is very odd as I even saved the working LinkedServer as TSQL script then executed it on the PROD server and with the EXACT same information for the linked server it fails to work.

I'll read up on the link you provided and keep my fingers crossed.

No in my case I'm not having an issue with impersonation. The credentials are all configured the same on both servers, yet my DEV server works while PROD fails...

Here is the error message I receive when I try to test the linked server connection:

"The test connection to the linked server failed."

Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "MaxersServer".
OLE DB provider "SQLNCLI" for linked server "MaxersServer" returned message "Unable to complete login process due to delay in opening server connection". (.Net SqlClient Data Provider)

Cant connect SQL2K named instance using OLE DB

Hi,

I am having a hard time trying to connect to a remote SQL Server 2000 named
instance using an OLE DB connection, the computer I am trying to connect
from has SQL Server 7 installed, but MDAC 2.6 SP1 (which should be
sufficient?). Errormsg below:

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.

/asp/test.asp, line 5

The remote server is listening on TCP/IP, port 1434

I am using a sql-login. The remote server is in mixed mode.

I've tried connect using Query Analyzer in order to troubleshoot the
problem, and came to the following conclusion:

- If i add an alias for the server in Client Network Configuration,
and configure the connection to use TCP/IP, 1434, then I'm able to
connect to the remote server using Query Analyzer. However,
my asp-page still won't work.

- If i don't add an alias, but run Client Network Utility and add
TCP/IP (port 1434) as first protocol, and Named Pipes second
protocol... then I am not able to connect using Query Analyzer or
the asp-page. How come?

The code in test.asp looks like this:
<%
dim objC
dim rs
Set objC = Server.CreateObject("ADODB.Connection")
objC.Open "Provider='SQLOLEDB.1';" & _
"Persist Security Info=True;" & _
"User ID='myusername';" & _
"Password='mypassword';" & _
"Initial Catalog=mydatabase;" & _
"Server=REMOTESERVER\INSTANCE;" & _
"Data source=REMOTE SERVER\INSTANCE"
objC.Execute "SELECT * FROM [dbo].[EverybodyListens_Employee] WHERE CGid =
'aviklund'"
%>

Some rows of the code above are wrapped.
REMOTESERVER is the remote server,
and INSTANCE is the instance name.

Thanks!

// BjrnThis http://msdn.microsoft.com/isapi/gosupport.asp?Target=/support/kb/articles/Q169/3/77.asp (KB Article) gives much insight to resolve the issue.

HTH