Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-03-05 : 08:56:39
|
| Paul writes "Promoting SLQ mail tasks from a development machine to a production machine.MS SQL 2000Windows 2000I have a local DTS that sends email. I used the "Send Mail" task button within the package editor to develop the email step.It was created and works great on my PC. The user it was intended for has a different story...The user has a shortcut that points to a VB script which executes 2 DTS procedures, the second of which is the mail DTS mentioned above. When they click the shortcut...everything appears to go well...they even get the completion message from a msgbox command at the end of the script. However, the first DTS produces its results, but the 2nd (the mail DTS) does not send the email.We set the mail DTS to keep logs and the following is what we found:Step Error Source: Microsoft Data Transformation Services (DTS) PackageStep Error Description:Logon failed: MapiLogonEx Failed due to MAPI error 273: MAPI Logon failed.Step Error code: 80040480Step Error Help File:sqldts80.hlpStep Error Help Context ID:700Once again, the mail DTS in question executes great both by itself and from within the VB script when it is my PC executing it. The users PC where it needs to work has no MS SQL components...do they need some component? Thanks for the help?" |
|
|
pdumas
Starting Member
1 Post |
Posted - 2002-03-05 : 10:23:35
|
| I am responding to my own posting...we found the problem:Within the DTS, the properties for the email ask for a "profile". DO NOT ASSUME...that the users of the DTS have a profile of the exact same name that you (the developer) have (locally). This property looks at your local profile names, then when it runs on another machine, it expects (as it should) to find the same exact local profile name on that machine.We developed the DTS and used "Microsoft Exchange Settings" as the profile, assuming everyone in our company had that local profile, but they did not. Once we added the local profile on the user machine, everything ran great. |
 |
|
|
|
|
|
SQL Mail