Solved

ODBC connetion to Exchange fails: Verify connection params / credentials?

Posted on 2006-11-20
9
660 Views
Last Modified: 2010-05-18
I am attempting to connect SQL Server 2005 (Express Edition) to a public folder of contacts on Exchange 2003 (both running on the same SBS server).

I have followed the instructions in SQL Server 2005 Online books: (http://msdn2.microsoft.com/en-us/library/ms191461.aspx) creating my link:

EXEC sp_addlinkedserver 'exchange', 'Exchange OLE DB provider', 'exoledb.DataSource.1', 'file:\\.\backofficestorage\localhost\public folders'

and then tried the simple query to verify the connection:

SELECT "urn:schemas:contacts:sn","urn:schemas:contacts:givenname"
FROM OpenQuery(Exchange, 'SELECT "urn:schemas:contacts:sn", "urn:schema:contacts:givenname" FROM SCOPE(''.\Common Contacts'')')

Everytime I do, I receive the following error:

Msg 7304, Level 16, State 2, Line 1
Cannot connect using OLE DB provider "Exoledb.DataSource" to linked server "Exchange". Verify the connection parameters or login credentials associated with this linked server.

The account i am using to login to SQL Server is an admin on the SBS Server as well as an owner of the Public Folder "Common Contacts".
What am i missing?!? This is very urgent!
0
Comment
Question by:mrtgold
  • 4
  • 3
9 Comments
 
LVL 30

Expert Comment

by:nmcdermaid
ID: 17985053
What is the SQL Server and SQL Serevr agent service running as? Temporaily change these to domain admin, stop and restart, and try it again.
0
 
LVL 2

Author Comment

by:mrtgold
ID: 17985175
Good suggestion - it was running as LocalSystem, but changing it to my account (I am a Domain Admin) didn't work  - still received exactly the same error message.
Created a new Domain Admin account and tried it with that - still same error.
0
 
LVL 30

Expert Comment

by:nmcdermaid
ID: 17985880
Did you try doing it to both SQL Server and SQL Server Agent accounts?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 2

Author Comment

by:mrtgold
ID: 17986959
Is there a SQL Server Agent with 2005? I don't see it in Services or in the SQL Server Configuration Manager and there is no sqlagent.exe process running...
I changed all the services that were there:
SQL Server
SQL Server Browser
SQL Server FullText Search (just in case...)
0
 
LVL 30

Expert Comment

by:nmcdermaid
ID: 17994196
I've got something called SQL Server Agent in my services, also I have SQL Server agent in Management studio.

Maybe you have the express version? Anyhow, that probably isn't it.


That document says:

>> the URL corresponding to the root folder of the Web Store

It sounds like there is some kind of web setup required first, are you aware of anything like that?


Also its a long shot but you could try removing the .1 from provider name as below:

EXEC sp_addlinkedserver 'exchange', 'Exchange OLE DB provider', 'exoledb.DataSource', 'file:\\.\backofficestorage\localhost\public folders'

The .1 is a version specific provider whereas without the .1 it will pick whatever provider version you have... though it is a long shot.

0
 
LVL 2

Author Comment

by:mrtgold
ID: 18055761
The lack of the SQL Agent is probably because of it being the Express Version.  I hope that is not the root cause of the problem be cause my client has emphatically stated he's not going to move to the full version.

"Web Store" refers to Exchange server and how you access data in there. I definitely have permissions to the Public Folder i'm attempting to access - or at least i've given both my login as well as the newly created Domain Admin account all privelages i can find - we are owners, administrators, clients, users, etc.

Already tried removing the .1 - no difference.

Given the project deadlines, i have all but abandoned this track and have begun on a different approach - building an intermediary synchronizing app that can access both the Exchange and the SQL datastores - but i really don't like this approach and would much rather use a real data provider so i'm still hoping that someone will come up with a solution...

Thanks,
tim
0
 
LVL 30

Accepted Solution

by:
nmcdermaid earned 500 total points
ID: 18058310
I suggest that you download FileMon from sysinternals.com and monitor the particular file that you are trying to open. This tool will tell you:

1. What account is trying to open it
2. Whether its successful.

FileMon is a very lightweight and eay to use tool. Even though your timelines are shrinking, its well worth having a go.

0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When you hear the word proxy, you may become apprehensive. This article will help you to understand Proxy and when it is useful. Let's talk Proxy for SQL Server. (Not in terms of Internet access.) Typically, you'll run into this type of problem w…
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function

832 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question