November 7, 2008 at 2:50 am
My SSIS (DTS) package runs a .bat file.
The log file states the following error:
Logon failed: MapiLogonEx Failed due to MAPI error 273: MAPI Logon failed.
Does anyone know what this means in layman terms?
Thanks
November 7, 2008 at 5:15 am
MAPI usually has to do with Email. At a guess, I'd say your .bat file is trying to use the old fashioned (and depreciated) SQL Mail from previous versions of SQL Server. And it's failing on the login because it can't get access to the email server.
SQL 2005 and most DBAs use SMTP mail. It's much more reliable. And DBMail (or the Send Mail task in SSIS) is pretty much SMTP mail.
Check for any mail tasks or scripts trying to send emails. That's probably where your error is.
November 7, 2008 at 6:27 am
Thanks for the clear info.
The BAT file:
dtsrun /Slocalql23\book /Usa /Peastcoat /N"Import" > e:\bookFTP\dtsftpscheduleV2.log
no referance to send email in BAT file.
Did you mean in the SSIS(DTS) package?
November 7, 2008 at 6:34 am
That's what it looks like. The .bat file appears to be running a package, so trace back to the package and see what you can find.
November 7, 2008 at 6:43 am
Ok so I have editied the package, it now seems to be erroring:
SSIS package "Package.dtsx" starting.
Error: 0xC002F210 at Execute procImportAllFiles UPDATE AND APPEND DATA, Execute SQL Task: Executing the query "execute procImportAllFiles" failed with the following error: "Import Updates Failed". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Task failed: Execute procImportAllFiles UPDATE AND APPEND DATA
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "Package.dtsx" finished: Failure.
November 7, 2008 at 6:51 am
Here's your main info:
"Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly"
First check the "UPDATE AND APPEND DATA" Execute SQL Task Parameters & Results tabs. If you don't have parameters or results, then your most likely issue is in the T-SQL or in a connection manager that is pointing to something that it can't see.
For T-SQL resolution, you'll have to cut-n-paste into SSMS and track down the problem that way. For Connection issues, try connecting to the server or pinging the server. I'm betting, though, given the original problem, this T-SQL is actually trying to send an email and can't find the email server.
November 7, 2008 at 6:58 am
Ok thanks for the prompt reply's!!
I am a total newbe to SSIS & DTS so im going to ask you some realy bumb questions now:
1. Where do I dind the "UPDATE AND APPEND DATA" Execute SQL Task Parameters & Results tabs??
2. the task the package is failing on does not use a SendMal teask... Its pointing to an SP which is importing data....
November 7, 2008 at 7:26 am
Edit the task. Look at the left side of it when it opens up. You'll have four "tabs". General, Paramters, Results and Expressions. Check each one. In General, the Results line directly affects what may or may not be in the Results tab. Also, on the Direct Input line, you have to have question marks for any parameters being passed into your stored procedure and if the parameters on the Parameters page are in the wrong order, then that'll cause a problem.
More info can be found in Books Online. As far as debugging the proc, I can't help you with that. You need to pull it into SSMS and debug it yourself. But check and see if there are results and parameters in the task first, that might be where your error is.
November 7, 2008 at 7:43 am
Thanks again, question:
How do I pull it into SSMS and debug it?
Please see screen shot
November 7, 2008 at 7:49 am
Do you have anyone who knows T-SQL in your organization? If so, you should go to them and ask them the best way to debug a stored procedure or a T-SQL query.
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply