Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error When Direct Mailer Database Name Contains Spaces


View products that this article applies to.

This article was previously published under Q308988

↑ Back to the top


Symptoms

When you attempt to use the Direct Mailer with a database whose name contains spaces, you may receive an error message.

↑ Back to the top


Cause

Names that include embedded spaces are not submitted correctly through the stored procedure that is submitted to the SQL server.

↑ Back to the top


Resolution

To resolve this problem, obtain the latest service pack for Microsoft Commerce Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
297216� INFO: How to Obtain the Latest Commerce Server 2000 Service Pack
The English version of this fix should have the following file attributes or later:
   Date         Time   Size     File name     
   --------------------------------------------
   Sep-28-2001  10:07  176,400  Listmanager.exe
				

↑ Back to the top


Workaround

To work around this problem, avoid using spaces in the file name that is required for the Direct Mailer. Note that if you surround the file name with brackets, the space in the file name is handled correctly.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Commerce Server 2000 Service Pack 2.

↑ Back to the top


More information

Steps to Reproduce Behavior

  1. Unpup a site that has spaces in database name.
  2. Create a Direct Mail campaign.
  3. Send a test mail from BizDesk Campaign Manager.
In the SQL Server event log, you see output that resembles the following:
 Event Type: Warning
 Event Source: SQLSERVERAGENT
 Event Category: Job Engine
 Event ID: 208
 Date: 8/20/2001
 Time: 4:41:28 PM
 User: N/A
 Computer: SystemName
 Description:
 SQL Server Scheduled Job 'TEST_CS_DM_name and namecontinued_1_0.535221' (0x99E99384DE206340913B918003B8BC2C) - Status: Failed - Invoked on: 2001-08-20 16:41:28 - Msg:  The job failed. The Job was invoked by User Admin. The last step to run was step 1 (TEST_CS_DM_name and namecontinued_1_0.535221_Step).
 
 Event Type: Error
 Event Source: Commerce Server 2000
 Event Category: None
 Event ID: 8196
 Date: 8/23/2001
 Time: 12:12:06 PM
 User: N/A
 Computer: SystemName
 Description:
 Commerce List Manager Error: 0x8C400003: Error while executing SQL/ADO
 operation: 0x80040E14 [OLE/DB provider returned Msg:  Deferred prepare could not be completed.][01000]
 Statement(s) could not be prepared.[42000]
 Incorrect syntax near the keyword 'and'.[42000]
				
In the SQL Profiler trace, you see output that resembles the following:
SQL Profiler trace:
 
 declare @P1 int
 set @P1=-1
 exec sp_prepare @P1 output, NULL, N'SELECT * from name and namecontinued _commerce.dbo.[LM_TEMP_C856C8C2_E066_4526_B758_9CE07981DE35]', 1
 select @P1
				

↑ Back to the top


Keywords: KB308988, kbhotfixserver, kbcommserv2000sp2fix, kbqfe, kbcommserv2000presp2fix, kbfix, kbbug

↑ Back to the top

Article Info
Article ID : 308988
Revision : 2
Created on : 9/23/2005
Published on : 9/23/2005
Exists online : False
Views : 422