Our users enter data into the MS Exchange database using custom Outlook forms. We want to import that data in SQL Server using SQL Server Data Transformation Services (DTS). We do not see Exchange in the Data Source list in the DTS wizard. Is there an easy way to do this? Maybe an OLEDB provider for Exchange?
I'm trying to find a way to import data from this data xml feed to get daily exchange rate. I' tried:
select * from openrowset(bulk 'http://www.bankofcanada.ca/stats/assets/xml/fx-noon.xml',single_blob) as x
Which is a feeble attempt at a start; however, am getting this error message:
Cannot bulk load because the file "http://www.bankofcanada.ca/stats/assets/xml/fx-noon.xml" could not be opened. Operating system error code 123(The filename, directory name, or volume label syntax is incorrect.).
Has anyone been able to solve the issue with setting up a package in EM, which connects to an Exchange(.edb) database and extracts the data into a SQL Server db. Previous message posts don't offer much insight. So far, all I have is using Access 2000, to connect & move the data, then extract from here. Thanks in advance for any help. BV
On my SQL Server 2000, I have successfully created a linked server to my Exchange 2000 server (located on the same physical computer). I can't send request and everything is fine.
But now, I would like to apply the "Impersonate" setting. The big problem I've got is that Exchange doesn't use a login and password for the authentification but use the Windows credentials.
I have try things like : login : <domain name><username> with the real password login : <username>@<internet domain name> with the real password but that doesn't work.
I would like to know if there is a way to "impersonate" user log on the SQL Server when they try to use the linked server to Exchange Server.
I'm using sql server 2005 and exchange 2003. End result is I want to upload email attachments to a table in sql. No one seems to have any idea how do do this except with .net, which i know nothing about so not really an option for me. I found this bit of info with some extensive web searching. Can anyone help fill in the blanks? I can't get the linked server to work yet.
EXEC sp_addlinkedserver 'exchange', 'Exchange OLE DB provider', 'exoledb.DataSource.1', 'file:\.ackofficestoragemailservernamepublic folders'
Error received:The OLE DB provider "exoledb.DataSource.1" has not been registered.
Hi All, I am having exchange server 2003. With following details.
1.Operating System 2003 standerd with sp2. 2.Exchange server 2003. Service pack don't know ( How to check)
From last 2 months, every two days my exchange server stops responding to clients.
When I check the services, all the Exchange related services are ON. ( they are running fine).
Then I use to Restart All excahnge related services, i.e Microsoft Exchange Information Store & Ms Exchange System Attended service and things starts working fine again.
This I have to do every 2 days.
I don't know why this is happening.
Can anyone assist me to resolve as it is getting critical day-by-day. Also How can I check which service pack of exchange is installed.
I am out of my element here but I have someone who is working on a project for me that entails him migrating our Access database to sql. He wants to load the sql software on our exchange server but our IT guy is saying this is not a good idea. Any thoughts???
Hi all, I'd like to link a SQL Server database / table to Microsoft Exchange Server E-Mail-Address data, for an Employee Directory project.
I've read a little about "Web Store", a little about ExOLEDB, but I've come across nothing along practical lines. I.e., I still don't know where to begin!
For example the "Web Store" should be created on the SQL server, but how do you create it? Any insights will be greatly appreciated.
I just read that if you use an exchange server...the account that youstart SQL with needs a mail on the exchange box.Is this true?I know I didn't need an account when I've set it up before...but Imight have been using a POP3 server.I have Outlook 2003 installed on the server. Windows 2003 Enterprise.Thanks.
Hello, I have created a MS Exchange 2000 link server in my MS SQL Server 2k. I have created a stored procedure (and a view...) using info from that linked server. When I am logged on the server as the Administrator, I can call my stored proc without any problems. When I use another computer (and I am not logged as the admin of the server) and I call the stored procedure, the following error is always raised : Server: Msg 7302, Level 16, State 1, Procedure test_proc, Line 3 " Impossible de créer une instance du fournisseur OLE DB 'exoledb.DataSource.1'. " <== I know it is a french error but it can be translated as : "Unable to instancied the OLE DB 'exoledb.DataSource.1' provider"
I would like to know if I can make run my stored proc in the admin account or what should I do to make it work
After a trust with exchange server established the xp_SendMailgives the following error:xp_sendmail: failed with mail error 0x80070005Prior to the trust everything worked fine.I have tried the following:1)Checking SQL and SQLAgents accounts all match up with default mailprofile.2)Confirmed I could send from outlook logged in under the account.3)xp_stopmail and xp_startmail4)restarted the SQL Agent5)Confirmed outlook settings as defined in:kb153159 -http://www.sqlnewsgroups.net/link.a...b/153159/EN-US/I also tried a pop3 account just to test, but no luck.I think what is happening is now that the trust is established when SQLmakes a mail contection it thinks it is user admin@<otherdomain> ratherthan admin@<normaldomain> and therefore thinks that agent account isdifferent than the mail account.Please help if you can.Thanks.
I would like to configure e-mail alerts on my SQL Server 2000 box.However, we also run Exchange on the same machine. I've been told therecould be conflicts/issues having Outlook on the same machine asExchange; and apparently, one needs Outlook to configure a mail profilefor SQL Server Agent.Is there, in fact, anything to worry about? If so, are there anywork-arounds beside moving Exchange to another server? (we've only gotone server, so this is not an option for us at this time).Thanks.- Dana
A view named "Viw_Labour_Cost_By_Service_Order_No" has been created and can be run successfully on the server. I want to import the data which draws from the view to a table using SQL Server Import and Export Wizard. However, when I run the wizard on the server, it gives me the following error message and stop on the step Setting Source Connection
Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success) - Setting Source Connection (Error) Messages Error 0xc020801c: Source - Viw_Labour_Cost_By_Service_Order_No [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0014019. There may be error messages posted before this with more information on why the AcquireConnection method call failed. (SQL Server Import and Export Wizard)
Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)
- Setting Destination Connection (Stopped)
- Validating (Stopped)
- Prepare for Execute (Stopped)
- Pre-execute (Stopped)
- Executing (Stopped)
- Copying to [NAV_CSG].[dbo].[Report_Labour_Cost_By_Service_Order_No] (Stopped)
- Post-execute (Stopped)
Does anyone encounter this problem before and know what is happening?
I am attempting to import data from Microsoft Access databases to SQL Server 2000 using the DTS Import/Export Wizard. I have a few errors.
Error at Destination for Row number 1. Errors encountered so far in this task: 1. Insert error column 152 ('ViewMentalTime', DBTYPE_DBTIMESTAMP), status 6: Data overflow. Insert error column 150 ('VRptTime', DBTYPE_DBTIMESTAMP), status 6: Data overflow. Insert error column 147 ('ViewAppTime', DBTYPE_DBTIMESTAMP), status 6: Data overflow. Insert error column 144 ('VPreTime', DBTYPE_DBTIMESTAMP), status 6: Data overflow. Insert error column 15 ('Time', DBTYPE_DBTIMESTAMP), status 6: Data overflow. Invalid character value for cast specification. Invalid character value for cast specification. Invalid character value for cast specification. Invalid character value for cast specification. Invalid character value for cast specification.
Could you please look into this and guide me Thanks in advance venkatesh imtesh@gmail.com
I am trying to simplify a query given to me by one of my collegues written using the query designer of Access. Looking at the query there seem to be some syntax differences, so to see if this was the case I thought I would import the database to my SQL Server Developer edition.
I tried to start the wizard from within SQL Server Management Studio Express as shown in one of the articles on MSDN which did not work, but the manual method also suggested did work.
Trouble is that it gets most of the way through the import until it spews forth the following error messages:
- Prepare for Execute (Error) Messages Error 0xc0202009: {332B4EB1-AF51-4FFF-A3C9-3AEE594FCB11}: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Could not start session. Too many sessions already active.". (SQL Server Import and Export Wizard)
Error 0xc020801c: Data Flow Task: The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009. (SQL Server Import and Export Wizard)
Error 0xc004701a: Data Flow Task: component "Source 33 - ATable" (2065) failed the pre-execute phase and returned error code 0xC020801C. (SQL Server Import and Export Wizard).
There does not seem to be any method of specifying a number of sessions, so I don't see how to get round the problem.
Does anyone know how I can get the import to work?
Has there been any indication from Microsoft as to when they anticipate using SQL 7.0 in SMS and Exchange? We are currently planning our MCSE+I certification training course schedules through the end of March. We are currently using SMS 1.2 and Exchange 5.5, which use SQL 6.5. We are planning to schedule the SQL 6.5 Admin and Design classes, but knowing when Microsoft will switch to SQL 7.0 for their BackOffice apps may influence our schedule. I have been told that we could take the SQL 7.0 Design class, and the instructor could tell us what has changed since SQL 6.5. I was told that the SQL 7.0 Admin class is very much different, however. Could anyone shed any light on this?
Does Exchange 2000 and SQL 2000 have to be the same machine to use exoledb.dll? I want to link to an Exchange server and gain access to a Public Folder Contact Object for use as a lookup table within an Access front end. Someone directed me to use the Exchange OLE DB Provider, but it does not exist on my SQL machine.
We have a business requirement for arching emails (5+ years) which are generated in an e-commerce application. The quantity is substantial and some of the emails will have MS Word attachments. As stands today, our Exchange 5.5 environment is already taxed and archiving options are limited. Someone suggested that there is a way to offload the emails into a SQL database. If we could do this, this would provide much more latitude.
Is there any way to run SQL Mail with exchange CLOSED? Keeping Exchange always minimized seems rather unneedy, inexperienced developers might just have the tendency to close it. Is there any way to avoid that?
Also, can SQL Mail be configured with something else besides Exchange?