strange net send problem
-
The net send job notifications have suddenly quit appearing.
These are on jobs that have been running for 4 years.
The messenger service is started on all machines involved; I can successfully net send from the command line; I can successfully test net send under SQL agent Operators.
I even re-created and tested the operators and it doesn't help. The problem arose around but not exactly the time we converted from sql7 to sql2k, but I think I have received the messages since then.
I'm going to ask our net admin but you know what his answer will be.
Any help will be appreciated.
Randy
-
Trt exec xp_cmdshell 'net send xxxxxx TEST' from QA.
I suspect the issue comes from the permission of xp_cmdshell.
-
Randy, I think Allen's on the right track. Have you checked that the user name under which the job is run has permissions to execute xp_cmdshell? And can you successfully run the job manually ? For those reading this who don't understand, the best way to check is, as Allen rightly states, to log in to Query Analyser *using the username that the job is running under* (you can find this from the job's Owner drop down in the General tab of the scheduling dialog), and see if you can run the xp_cmdshell command from there. If it doesn't work, then that's most likely your problem, you'll need to change the Owner in the scheduling dialog's General tab to one which can successfully run the xp_cmdshell.
You might also want to right click on the job after running it manually, look at View Job History and click on Show step details - it might tell you something useful which just the absence of the net send message appearing doesn't reveal.
If it still doesn't work, then if practical try re-creating the job - we've had a number of 7->2000 job execution issues that have been fixed that way.
Jon -
Journeyman, try restarting the messenger service. We have ancountered similar problems: Net send works fine for awhile then users ( and not necessarily all of them ) stop getting notifications. Even though messenger service is running once we restart it, all notifications resume.
Hope this helps,
dab
-
I re-created the job and the notification still did not occur.
I tried xp_cmdshell in QA without success.
I set up a test job to execute xp_cmdshell on our sql2k and on our sql7 server. It worked on the sql7 but not on the sql2k server.
I got this error message in QA:
An error occurred while sending a message to <machine name>.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273.
Our Net Admin researched this and apparently this is a problem that was fixed with Win2K sp2. We have been at the latest service pack for awhile. The NA speculates that a hotfix applied recently might have affected the problem that sp2 fixed. He may be compelled to reinstall the service packs.
-
run netsend directly from the dos command line. this will ensure that it still actually works. then concentrate on SQLServer side.
-
Try another recipient name. The error states
"The message alias could not be found on the network." Maybe the network guys changed the name you've been using.
-
Let me re-iterate. Have you restarted the messenger service?
-
DAB wrote:
<<Let me re-iterate. Have you restarted the messenger service? >>
SUCCESS!
I just restarted the messenger service and ran my test job and it worked. I don't know how I missed your earlier reply, but I am glad you "re-iterated".
Thanks a bunch!
-
I am facing the same problem when I send the message to a computer outside the network ....my question is :
HOW can I send an net send and even if the user Pc name is not available in the netwrok ??????
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply