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 |
|
panthagani
Yak Posting Veteran
58 Posts |
Posted - 2007-05-15 : 13:12:31
|
| I am trying to execute a stored procedure on Server1 which creates an excel report on a share of Server2:The following error message is thrown:Saving of scheduled report(s) to Excel file failed : 203 SaveReportToExcel() in TlRptToFile.RptExcel failed in sproc_SaveReportAsFile - TLRptXL::SaveReportToExcel - Connection to Database failed for Analytics DataBase Server : TKTALSQL3, Application Server: and DataBase : tlAnalytics : Windows Error - The system could not find the environment option that was entered.A DCOM component on Server1 runs the stored procedure that creates the excel report. The account under which DCOM component runs is a member of 'Administrators' group on both Server1 and Server2. Checked permissions on the shares. Account is a local Admin on both Server1 and Server2. Account under which SQLServer and ServerAgent runs is also an Admin on these shares (implicitly as part of 'Administrators' group).I am manually able to create an excel/text file on the Server2 share while accessing it from Server1, though.Appreciate your help in resolving the issue. |
|
|
panthagani
Yak Posting Veteran
58 Posts |
Posted - 2007-05-15 : 13:23:10
|
| Forgot to add: Both Server1 and Server2 have an SQL Server version of 8.00.2151 (SP 4 + hotfix 903742). The above described issue started very recently, 12 hours back.Thank you. |
 |
|
|
Jeff Moden
Aged Yak Warrior
652 Posts |
Posted - 2007-05-15 : 19:19:34
|
| Did someone change the login the server uses to start the SQL Server Service?--Jeff Moden |
 |
|
|
panthagani
Yak Posting Veteran
58 Posts |
Posted - 2007-06-17 : 20:12:02
|
| Thanks Jeff. It was an internal Windows account permissions issue and not SQL server related. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-06-17 : 20:32:04
|
| Try start sql with your account on server1 and run the sp again. If works, it's sql service account's permission issue. |
 |
|
|
|
|
|