January 23, 2005 at 10:43 am
We have both SQL 7 and SQL 2000 running on W2K Servers running sp_runwebtask that write the output to a "mapped" drive on the W2K Server.
When we tried the exact same thing with SQL 2000 on a W2K3 Server, sp_runwebtask says that it cannot access the "mapped" drive. If the template file and the output file are put on the local server drives, it works. The files that are being accessed CAN be opened/updated in notepad, so permissions to the mapped drive are not the problem.
All versions (W2K and W2K3) have SQL running as Domain Administrator account.
This is a show-stopper in noving to W2K3 Servers.
Ferrell
January 26, 2005 at 8:00 am
This was removed by the editor as SPAM
January 27, 2005 at 11:03 am
I used Enterprise Manager wizard to create web task and then scripted it. Here is the script and it worked fine, as well as job with SQL 2000 and Windows 2003:
EXECUTE sp_makewebtask @outputfile = N'\\testsrv\test\WebPage1.htm', @query=N'SELECT [city], [zip] FROM [authors]', @fixedfont=1, @HTMLheader=3, @webpagetitle=N'Microsoft SQL Server Web Assistant', @resultstitle=N'Query Results', @dbname=N'pubs', @whentype=4, @targetdate=20050127, @targettime=184524, @dayflags=1, @numunits=1, @unittype=3, @rowcnt=20,@procname=N'pubs Web Page',@codepage=65001,@charset=N'utf-8'
USE MSDB
GO
EXEC sp_runwebtask @procname = N'pubs Web Page'
The only things are: I used UNC path, not mapped drive letter in script and by default share permissions was just "read" for everyone (I added "full" for SQL and it works fine). To check if permissions are OK for network drive - run from Query Analyzer:EXEC xp_cmdshell 'dir \\testsrv\test'
January 27, 2005 at 12:43 pm
Svetlana
Thank you very much.
We ended up calling Microsoft - there IS a bug in SQL 2000 SP3a that caused the problem. Anyone needing the fix should request KB884856 fix to SQL 2000 SP3a - it fixed our problem with using a "mapped-drive".
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply