I just installed the SQL Server 2005 eval version on my laptop to try it out and now Outlook crashes. There appears to be a conflict with Outlook Business Contact Manager, which might be running its own database under the covers.
When I try to start Outlook I get the error message "Business Contact Manager has encountered a problem and needs to close. We are sorry for the inconvenience". The button choices are Debug, Send Report Later and Don't Send. Clicking Don't Send closes Outlook.
I found some info on modifying the registry to disable BCM, which I did, but I still get the same error and Outlook won't start. I also tried removing all of the SQL Server 2005 stuff from my path environment variable but it didn't work either.
Any suggestions would be appreciated because I depend on Outlook for my email and contacts.
I have a Reporting Services 2005 report that is emailed to users. I created/formatted the report based on how it looked in Outlook 2003 which all of our users had at that time. The report is wide, but just fit in the email window when it was full size. Now I have a user who has been converted to Outlook 2007 and he emailed me a copy of the report he received in Outlook 2007 and it looks like it reduced the column sizes; it does not fill the entire email window and wraps the wording on most lines because the column sizes have been reduced.
SP2 for SQL Server 2005 x64 has been less than happy for me.
The initial problem, mentioned in another thread, concerned SSIS client which stopped liking Data Flow components. It was solved by a removal and reinstallation of the client tools.
However, there now seems to be a problem with making use of the Teradata oledb provider within SSIS. Prior to the installation of SP2 there was no problem.
I create a new SSIS package Add a Data Flow component Within the data flow add an oledb source Create a new connection - using the Teradata oledb provider Test the connection (it works!) Use SQL something like "select * from some_teradata_table_on_the_TD_server" Click on columns, wait a second, a list of columns is returned Add a SQL Server destination (with a new SQL Server connection) Connect the two components Save the package
Click go The TD oledb source component turns bright red and the error is "class not registered"
I have uninstalled the TD oledb provider (and underlying TD components) and re-installed (32-bit and 64-bit) - no change
I have just upgraded to SQL Server 2005 from SQL Server 2000.In Microsoft SQL Server Management Studio, when I click on databaseproperties, I receive the following error:-Cannot resolve the collation conflict between"Latin1_General_CI_AS"and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.(Microsoft SQL Server, Error: 468)Some reference suggest that I can change the database collation byclicking database properties!What can I do?
Can anyone recommend a source of info on connecting Outlook to a SQL database of contacts? Also interested in third party tools/solutions that I could just buy and customize.
I need to be able to get at data from my own VB apps, but it would be nice to dump contacts into Outlook for people taking laptops and CE machines on the road. Even nicer if they could use Outlook to update addresses and upload to SQL Server.
we have Reporting services and Office Sharepoint on the same server, but the reporting services website is on default website and won't start because MOSS is already using the port. can i just change SSRS website port ?
I (absolute beginner) configured a distribution on a publisher wich acts as its own distributor. I did it by right click on replication "configure distribution", followed all instructions and chose all default values. Nothing more. But now I want to view the distributor properties and following message appears:
SQL Server is unable to complete the Distributor Properties.
ZUSÄTZLICHE INFORMATIONEN:
Ausnahme beim Ausführen einer Transact-SQL-Anweisung oder eines Transact-SQL-Batches. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. (Microsoft SQL Server, Fehler: 468)
My collegue has no problems viewing these properties. We have both XP and SQLServer 2005 SP1. What is the reason for this error message? And how can I solve it?
Just recently my SQL server agent has been causing problems with my Outlook. When the Agent is started, it causes all processes on Outlook to hang. As soon as I stop the Agent, then Outlook works just fine again. Does anyone know a possible cause for this. Up until a couple days ago things were working just fine, and then this problem seems to have popped out of nowhere.
Guys Does anyone know of a 3rd party module/plug-in for VS or even some downloadable code that enables the import of Outlook/ACT and similar contact information through an ASP.NET page into a SQL Server table with ongoing 1-click button sync.
I need to replicate something similar to the Intellisync tool used in Yahoo Mail.
Outlook says 'to prevent your privacy outlook prevented the image download' I don'y want users to right click and download image from the 'empty box'.Here is my code:
is it possible to write a script for Microsoft outlook that will execute a query to an sql server 2005 and populate a public "contacts" folder?
i know there are expensive syncing applications, but i would just like to script and buttonize the manual export-import process.
is it possible? macros? what is required? ADO/DAO/other is there a basic example of this or just a script sample of connecting and retrieving a dataset from the server?
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
When I launch Outlook, it takes forever for the program to finally open. With any inbound email, it stops processing whatever is underway at the time....and frequently there is a 2-3 second lag between keyboard input and what appears on the screen. SQLserver is usually consuming upwards of 1-gb of memory....help. Mike
I am facing the Follwing error: Cannot resolve the collation conflict between "Latin1_General_BIN" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Follwing is my Code: code]select * from #temp_Table a where ltrim(rtrim(Model_ID))+''+ltrim(rtrim(Set_Serial_Number)) in (select ltrim(rtrim(b.Model_SerialNo)) from #temp_Table2 b where b.Auto_Id=1)[[/code]
I'm having some problems getting Interactive Conflict Resolution working under SQL Server 2000 SP4. I have set "Allow Subscribers to resolve conflicts interactively" under the Resolver tab for the article in the publication. I have set "Enable synchronization using Windows Synchronization Manager" and "Resolve conflicts interactively" under the Synchronization tab for the subscription. I have set "Resolve conflicts interactively" under the Other tab for the subscription properties in the Windows Synchronization Manager. However, when I generate conflicting data in the publishing and subscribed DBs and synchronize using the manager, the resolution is automatic and a warning pops up informing me that "conflicts occurred while syncronizing the data and were resolved according to defined rules." Am I missing anything here?
I am practicing on vmware 2 node failover cluster for doing Sql failover clustering understanding.I did proper Ad Dc setup and configured san storage through iscsi software that I downloaded from net.I did target and initiator configuration for san storage on same Domain controller vm.Name of target is Target1 and has two initialtor for node1 and node2.It has two virtual disk assigned Quorumdisk.vhd and sqldisk.vhd.ON vmnode1 I have initialzed and formatted my both disk with proper volume and label.
Node which are participating in cluster are node1 and node2.while my windows clustering went fine,while Sql server installation on node 1,i got error IP Address conflict occured.
my DC has IP address:192.168.1.10 my Node1 is 192.168.1.20 node2:192.168.1.30 Cluster IP address is 192.168.1.35
What has cause this situation.What configuration is needed.How do I troubleshoot this problem as now I can not install my sql for clustering as also gave me Invalid network name error.Is my storage configuration not proper or IP address is in correct?Do I need to put my virtual disk in Clustered shared volume?
On our SQL 7.0 servers we have always used Outlook 97 as our mail client and until last week we've had no issues with this setup.
A week ago a number of the servers with this set up started hanging on jobs with mail statments using xp_sendmail and the only solution was to reboot the server. All the servers use the same NT account and the same mail box for the mail. I've talked with our Exchange guys and they say that nothing has changed on the mail server. I found a Q article (Q315886) that suggests starting sql as an application not a service to see if pop ups could be causing the problem. Well no pop ups.
I installed Outlook 2000 on the boxes and that seems to have fixed it. Or at least no problems today with those servers.
Has anyone seen this before or have any idea what might be the cause of it?
Anyone ever setup the OutLook Express client to use SQL Mail ? I'm able to send messages via OutLook Express; however, SQL Mail doesn't recognize any profiles.
In using OutLook Express do I need to also setup a PostOffice. My server currently doesn't have any POST OFFICE or Mail software under control panel.
I have a question that I hope to get an answer from you.
We had an exchange central which used to get data from the outlook and save it in the database, then we have another solution that filters the data we need from there and save it into another database to produce a report for the economy department to be used for wages. Now the exchange central has many problems and they decided not to use it any more. What I want to do is to get data(calendar posts) direct from the outlook into my SQL 2000 database. Is it possible? If yes, what is the best approach to do?
I am trying to build some sort of interface either directly in MS Outlook on the client comp. or a stand-alone app. The requirement works somewhat like what is done between a PDA and MS Outlook, with the exception that the data only goes one way - SQL Server --> Outlook.
I want to allow for the user to choose from their data in SQL Server and have it bring that data down into their contacts folder. It will need to work over the internet, and MS Exchange is not a preferred method.
Clients are not on the same network as the server, they only connect to the internet via IP and use simple POP mail accounts.
Does anyone know the 'trick' in getting sqlmail (sqlserver 7.0) to work with Outlook 2000 on a windows 2000 server machine. I've setup a mail profile on Outlook, but it is not listed in the dropdown menu in the sqlmail properties. Outlook communicates with my smtp/pop3 mail server - no problem. I can't get sqlmail to interface with outlook. Basically it is telling me that it cannot find ANY profiles on the server.
I'm trying to make SQLMail work. I have installed Microsoft Outlook 98 with MSSQL 7.0 on a NT Server 4.0 with Service Pack 6. I have set a profile for a user with admin rights to start a service. I can successfully start up with SQL with this account. When I try to start up SQL Mail it comes back with this error:
DESCRIPTION: Error: 0, Severity: 19, State: 0 SqlDumpExceptionHandler: Process 34 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
With another dialog box: Error 22030: A MAPI Error (error number: 87) occured:
Can any one Help?? Do I need reapply the service pack??
We do not have any licenses for MS Outlook and our main e-mail client is GroupWise. Someone has told me that we should be able to use the Outlook Express client to activate SQL Mail. Is this true; if so how is it done. If not does it make since to put the GroupWise client on the SQL Server ?
I'm trying to set up Sql Mail using Outlook 2000 and the only way I can get a message sent is to have the Outlook client open at the time I start Sql Mail. Sql Mail will start regardless of the profile chosen even if it is blank, but if the Outlook client was not running at the time I started Sql Mail then while executing xp_sendmail I get "Server: Msg 17914, Level 18, State 1, Line 0 Unknown recipient: Parameter '@recipients', recipient 'jcorriveau@homeruns.com'"
Regardless of the Outlook client status or profile setup when performing a MAPI profile test, <SQL MAIL><Properties><Test>, I receive "SQL-DMO(ODBC SQLState: 42000) Error 22030: A MAPI error(error number 273) occurred.:Unable to get the default MAPI Message Store due to MAPI error 273:The information store could not be opened."
I've setup Sql Mail and Outlook 97/98 clients in the past and have not had to have the client open when starting Sql Mail. I've read most of the technet and knowledge base articles and the only ref I can find to this problem is a note in Q248431 "note that outlook 2000 or another configured MAPI client must be started before xp_startmail is executed." Was this the case in Outlook 97/98?
The Exchange server is in another domain. I think it's version 5.5. I'm using my domain account and profile to setup Sql Mail. I can send and receive mail fine using Outlook 2000. There is a Password dialog box that appears when starting the Outlook client prompting for User Name, Domain Name, and Password. I have not been able to create a profile that gets around this dialog box. Is this an Exchange server setting? If so, is it a server wide setting or can it be disabled per mail account?
Any help with this will be appreciated. Thanks, Jim
We have a SQL 2000 cluster running on WIn2003. in a normal sql install you install Outlook client on SQL Server for Agent to use to send messages. Do you have to do something different for a clustered environment?
My IT manager doesn't like the idea that a production process written in DTS needs Outlook 2000 running for DTS Email. I tend to agree that having an app like Outlook 2000 running in the production machine is kind of tacky. Am I missing something here? Why would MS suggest such a solution? Is there a way to configure DTS and Outlook so Outlook doesnt have to be running as an app?
I'm sending data from a simple query using xp_sendmail and the @query variable to send via Outlook 2000. Everthing is fine data-wise, but the font of the data is wrong in the e-mail causing the columns of data to be justified all over the place.
I would like it to send in 'courier new' font to fix this problem, but SQL server defaults to use plain txt so the e-mail client receiving the information is not forced to use the font and uses its own default (which again throws the alignment out). I need to make it use the 'Rich Text' format to enforce this but SQL seems to bypass this when sending via sp_sendmail.
I know this is more an Outlook problem, but it is the way SQL 2000 uses it that is my issue here
Is there a way to export a list of email addresses to outlook based on certain query conditions? So for example, lets say using pubs, I want to send out an email to a group of authors who have published only one book. So could I essentailly query for the authors and then have those corresponding authors emails sent to outlook so that I could send out a generic email asking them if they are going to write another book or something like that?
