October 13, 2005 at 1:13 pm
We are running sql 2000 sp3 on a win2003 server. Let's call this server a.
We configured the SQl 2000 client on another server (server b) and we are trying to get that server to send SQl Mail with an attachment that is on a mapped drive (server c).
The client on server b links to server a. We use the same domain acct for both server services and we made sure the domain acct and the acct we log onto server b both have rights to the attachment on server c.
When we run xp_sendmail on server B using a local attachment, it works.
It only fails when we try to reference the attachment on the mapped drive. And yet as far as we can tell, the rights are correct.
Any clues?
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
October 13, 2005 at 1:47 pm
instead of referencing a mapped drive use the full unc path:
\\servername\drivename\folder\etc
October 13, 2005 at 2:18 pm
Tried this. Still same error number 18025. Micro$oft has some knowledge base articles about this, but not for my specific problem.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
October 13, 2005 at 2:57 pm
OK, maybe I'm dim but this confuses me:
"We configured the SQl 2000 client on another server (server b)"
Do you mean you're using Query Analyzer on Server b to attach to SQL Server on server a and when you do "EXEC xp_sendmail..." ?
Or did you mean to say you have SQL2000 Server on server b as well?
If so was that also SP3?
Can you do this: "EXEC xp_cmdshell 'dir [mappeddriveletter]:\path'" and have it work?
(that is, what are the permissions of the account that the sql service is running under?)
October 13, 2005 at 3:17 pm
<sigh>
Server b only has the SQL server client tools installed...
we are running xp_sendmail on that server. We registered Server a's database
on server b. Both have sp3.
The sql server account has read and write permissions on the folder where the attachment lives (on server c).
The XP_CMDSHELL command does not work. The error message is 50001.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
October 13, 2005 at 4:08 pm
OK this does not compute:
"Server b only has the SQL server client tools installed...
we are running xp_sendmail on that server. "
xp_sendmail will only run on an actual SQL Server box. If you do not have SQL 2000 Server software (as opposed to "client" software) installed on server b then you cannot possibly be running it on server b. (You can only access --and run it on-- server a.)
Whatever...
It's also not clear what you mean by xp_cmdshell not working. Error messages are in words, error numbers are numbers. Is the 50001 a SQL error? (as far as I know this is not in the range of system errors in SQL) Is it a DOS error that prints out from the xp_cmdshell (that is xp_cmdshell works, but the DOS command didn't)?
You need to learn to be much more clear in what's going on.
I have no idea what is meant by "We registered Server a's database".
October 13, 2005 at 5:22 pm
Sorry we don't speak the same language.
You can run xp_sendmail from a server connected to a sql database on another server. You need rights to EXECUTE commands from the master database for this to work. it does..believe me.
The error message was a number - sorry to disappoint you...and yes it doesn't seem to be in the range of SQl errors.
Let's stop here.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply