I'm asking this question for a client of mine. They have SQL 2005 running on
a new server and have the AGENT running under a local server username - not a
network username.
They are trying to create a job under the agent and the only username that
appears in the drop-down for the step is this local server username. They
are trying to copy a file to a network share and this local un does not have
access to the share. How do you get more un's listed for the agent steps?
What is best practice in the field for what to have the agent run as?
I've always thought that having it run under a domain account would mean
that the domain server had to be up and running for SQL to be alive - not
like that's a problem - or is it?
What do you all do?
The SQLServerAgent runs under a domain account for us, that has writes to all
SQL Server Admin folders. I woulder perfer to minimize the control a bit,
but I think domain account is required. If PDC does go down, well I think
SQL will be least of the problems ;-).
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Steve Z" wrote:
> I'm asking this question for a client of mine. They have SQL 2005 running on
> a new server and have the AGENT running under a local server username - not a
> network username.
> They are trying to create a job under the agent and the only username that
> appears in the drop-down for the step is this local server username. They
> are trying to copy a file to a network share and this local un does not have
> access to the share. How do you get more un's listed for the agent steps?
> What is best practice in the field for what to have the agent run as?
> I've always thought that having it run under a domain account would mean
> that the domain server had to be up and running for SQL to be alive - not
> like that's a problem - or is it?
> What do you all do?
Showing posts with label local. Show all posts
Showing posts with label local. Show all posts
Saturday, February 25, 2012
Agent jobs that copy files to network shares
I'm asking this question for a client of mine. They have SQL 2005 running on
a new server and have the AGENT running under a local server username - not a
network username.
They are trying to create a job under the agent and the only username that
appears in the drop-down for the step is this local server username. They
are trying to copy a file to a network share and this local un does not have
access to the share. How do you get more un's listed for the agent steps'
What is best practice in the field for what to have the agent run as?
I've always thought that having it run under a domain account would mean
that the domain server had to be up and running for SQL to be alive - not
like that's a problem - or is it?
What do you all do'The SQLServerAgent runs under a domain account for us, that has writes to all
SQL Server Admin folders. I woulder perfer to minimize the control a bit,
but I think domain account is required. If PDC does go down, well I think
SQL will be least of the problems ;-).
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Steve Z" wrote:
> I'm asking this question for a client of mine. They have SQL 2005 running on
> a new server and have the AGENT running under a local server username - not a
> network username.
> They are trying to create a job under the agent and the only username that
> appears in the drop-down for the step is this local server username. They
> are trying to copy a file to a network share and this local un does not have
> access to the share. How do you get more un's listed for the agent steps'
> What is best practice in the field for what to have the agent run as?
> I've always thought that having it run under a domain account would mean
> that the domain server had to be up and running for SQL to be alive - not
> like that's a problem - or is it?
> What do you all do'
a new server and have the AGENT running under a local server username - not a
network username.
They are trying to create a job under the agent and the only username that
appears in the drop-down for the step is this local server username. They
are trying to copy a file to a network share and this local un does not have
access to the share. How do you get more un's listed for the agent steps'
What is best practice in the field for what to have the agent run as?
I've always thought that having it run under a domain account would mean
that the domain server had to be up and running for SQL to be alive - not
like that's a problem - or is it?
What do you all do'The SQLServerAgent runs under a domain account for us, that has writes to all
SQL Server Admin folders. I woulder perfer to minimize the control a bit,
but I think domain account is required. If PDC does go down, well I think
SQL will be least of the problems ;-).
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Steve Z" wrote:
> I'm asking this question for a client of mine. They have SQL 2005 running on
> a new server and have the AGENT running under a local server username - not a
> network username.
> They are trying to create a job under the agent and the only username that
> appears in the drop-down for the step is this local server username. They
> are trying to copy a file to a network share and this local un does not have
> access to the share. How do you get more un's listed for the agent steps'
> What is best practice in the field for what to have the agent run as?
> I've always thought that having it run under a domain account would mean
> that the domain server had to be up and running for SQL to be alive - not
> like that's a problem - or is it?
> What do you all do'
Agent jobs that copy files to network shares
I'm asking this question for a client of mine. They have SQL 2005 running o
n
a new server and have the AGENT running under a local server username - not
a
network username.
They are trying to create a job under the agent and the only username that
appears in the drop-down for the step is this local server username. They
are trying to copy a file to a network share and this local un does not have
access to the share. How do you get more un's listed for the agent steps'
What is best practice in the field for what to have the agent run as?
I've always thought that having it run under a domain account would mean
that the domain server had to be up and running for SQL to be alive - not
like that's a problem - or is it?
What do you all do'The SQLServerAgent runs under a domain account for us, that has writes to al
l
SQL Server Admin folders. I woulder perfer to minimize the control a bit,
but I think domain account is required. If PDC does go down, well I think
SQL will be least of the problems ;-).
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Steve Z" wrote:
> I'm asking this question for a client of mine. They have SQL 2005 running
on
> a new server and have the AGENT running under a local server username - no
t a
> network username.
> They are trying to create a job under the agent and the only username that
> appears in the drop-down for the step is this local server username. They
> are trying to copy a file to a network share and this local un does not ha
ve
> access to the share. How do you get more un's listed for the agent steps?
?
> What is best practice in the field for what to have the agent run as?
> I've always thought that having it run under a domain account would mean
> that the domain server had to be up and running for SQL to be alive - not
> like that's a problem - or is it?
> What do you all do'
n
a new server and have the AGENT running under a local server username - not
a
network username.
They are trying to create a job under the agent and the only username that
appears in the drop-down for the step is this local server username. They
are trying to copy a file to a network share and this local un does not have
access to the share. How do you get more un's listed for the agent steps'
What is best practice in the field for what to have the agent run as?
I've always thought that having it run under a domain account would mean
that the domain server had to be up and running for SQL to be alive - not
like that's a problem - or is it?
What do you all do'The SQLServerAgent runs under a domain account for us, that has writes to al
l
SQL Server Admin folders. I woulder perfer to minimize the control a bit,
but I think domain account is required. If PDC does go down, well I think
SQL will be least of the problems ;-).
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Steve Z" wrote:
> I'm asking this question for a client of mine. They have SQL 2005 running
on
> a new server and have the AGENT running under a local server username - no
t a
> network username.
> They are trying to create a job under the agent and the only username that
> appears in the drop-down for the step is this local server username. They
> are trying to copy a file to a network share and this local un does not ha
ve
> access to the share. How do you get more un's listed for the agent steps?
?
> What is best practice in the field for what to have the agent run as?
> I've always thought that having it run under a domain account would mean
> that the domain server had to be up and running for SQL to be alive - not
> like that's a problem - or is it?
> What do you all do'
Friday, February 24, 2012
after upgrading to sept ctp 2005 reports with subreports fail
I just installed September 2005 CTP and all reports with subreports
getting an error:
Error occured during local report processing. An internal error occured
on the report server.
If i delete subreports everything is fine. The error log says
following:
09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3444
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x47405858
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0001.mdmp
09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3444
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x11A21E9C
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0002.mdmp
09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2732
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x10B35858
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0003.mdmp
09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
Any ideas?
Everything was fine in June CTP versionDid you upgrade the June CTP or did you remove everything (including the
dotnet 2.0 framework beta) first?
This CTP does not upgrade, you have to remove everything first and then
install.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126801637.855296.186610@.g49g2000cwa.googlegroups.com...
>I just installed September 2005 CTP and all reports with subreports
> getting an error:
> Error occured during local report processing. An internal error occured
> on the report server.
> If i delete subreports everything is fine. The error log says
> following:
> 09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x47405858
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0001.mdmp
> 09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x11A21E9C
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0002.mdmp
> 09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 2732
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x10B35858
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0003.mdmp
> 09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
> Any ideas?
> Everything was fine in June CTP version
>|||removed everything twice and reinstalled|||I just created one (report/subreport). I suggest trying recreating the
report from scratch (or at least the subreport and then re-embed it).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126803423.272541.149830@.g47g2000cwa.googlegroups.com...
> removed everything twice and reinstalled
>|||that what i did also. did not help.
here is another hint:
if i put this subreport under the group footer (or header) that i want,
report fails.
If i move subreport to different group header it works.|||If you email me the rdl and rdl.data files for both report and subreport I
will see about getting it to the correct person at MS. Just remove NOSPAM
from my email address.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126807105.990018.151820@.z14g2000cwz.googlegroups.com...
> that what i did also. did not help.
> here is another hint:
> if i put this subreport under the group footer (or header) that i want,
> report fails.
> If i move subreport to different group header it works.
>|||before I'll do this try to reproduce it this way:
create report with 4 groups:
Group1
Group2
Group3
Group4
create subreport
put subreport under group 4 (or 3, header, footer, detail - does not
matter)
report will not run (at least for me)
if you put it inder group 1 or 2, report will work in Sept CTP 2005
package|||Great repro. I will pass it on to MS.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126879282.885405.84350@.g47g2000cwa.googlegroups.com...
> before I'll do this try to reproduce it this way:
> create report with 4 groups:
> Group1
> Group2
> Group3
> Group4
> create subreport
> put subreport under group 4 (or 3, header, footer, detail - does not
> matter)
> report will not run (at least for me)
> if you put it inder group 1 or 2, report will work in Sept CTP 2005
> package
>|||now, i think i know what really happened:
I have 4 groups
Group1
Group2
Group3
Group4
if one of the values for Group4 ( in my case Group3 also) will be null,
subreport that you will put under this group will make main report to
fail. And it happens only in Sept CTP 2005 package|||Great, I'll make sure someone gets this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126887557.215825.300160@.f14g2000cwb.googlegroups.com...
> now, i think i know what really happened:
> I have 4 groups
> Group1
> Group2
> Group3
> Group4
> if one of the values for Group4 ( in my case Group3 also) will be null,
> subreport that you will put under this group will make main report to
> fail. And it happens only in Sept CTP 2005 package
>|||hi, i have hit this same problem as well. has a fix or workaround been
identified yet?
thanks,
steve
"bosstan1@.gmail.com" wrote:
> I just installed September 2005 CTP and all reports with subreports
> getting an error:
> Error occured during local report processing. An internal error occured
> on the report server.
> If i delete subreports everything is fine. The error log says
> following:
> 09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x47405858
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0001.mdmp
> 09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x11A21E9C
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0002.mdmp
> 09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 2732
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x10B35858
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0003.mdmp
> 09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
> Any ideas?
> Everything was fine in June CTP version
>|||Has anyone found a solution to this? I am running into the same issues.
"Bruce L-C [MVP]" wrote:
> Great, I'll make sure someone gets this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <bosstan1@.gmail.com> wrote in message
> news:1126887557.215825.300160@.f14g2000cwb.googlegroups.com...
> > now, i think i know what really happened:
> > I have 4 groups
> > Group1
> > Group2
> > Group3
> > Group4
> >
> > if one of the values for Group4 ( in my case Group3 also) will be null,
> > subreport that you will put under this group will make main report to
> > fail. And it happens only in Sept CTP 2005 package
> >
>
>
getting an error:
Error occured during local report processing. An internal error occured
on the report server.
If i delete subreports everything is fine. The error log says
following:
09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3444
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x47405858
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0001.mdmp
09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3444
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x11A21E9C
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0002.mdmp
09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2732
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x10B35858
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0003.mdmp
09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
Any ideas?
Everything was fine in June CTP versionDid you upgrade the June CTP or did you remove everything (including the
dotnet 2.0 framework beta) first?
This CTP does not upgrade, you have to remove everything first and then
install.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126801637.855296.186610@.g49g2000cwa.googlegroups.com...
>I just installed September 2005 CTP and all reports with subreports
> getting an error:
> Error occured during local report processing. An internal error occured
> on the report server.
> If i delete subreports everything is fine. The error log says
> following:
> 09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x47405858
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0001.mdmp
> 09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x11A21E9C
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0002.mdmp
> 09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 2732
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x10B35858
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0003.mdmp
> 09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
> Any ideas?
> Everything was fine in June CTP version
>|||removed everything twice and reinstalled|||I just created one (report/subreport). I suggest trying recreating the
report from scratch (or at least the subreport and then re-embed it).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126803423.272541.149830@.g47g2000cwa.googlegroups.com...
> removed everything twice and reinstalled
>|||that what i did also. did not help.
here is another hint:
if i put this subreport under the group footer (or header) that i want,
report fails.
If i move subreport to different group header it works.|||If you email me the rdl and rdl.data files for both report and subreport I
will see about getting it to the correct person at MS. Just remove NOSPAM
from my email address.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126807105.990018.151820@.z14g2000cwz.googlegroups.com...
> that what i did also. did not help.
> here is another hint:
> if i put this subreport under the group footer (or header) that i want,
> report fails.
> If i move subreport to different group header it works.
>|||before I'll do this try to reproduce it this way:
create report with 4 groups:
Group1
Group2
Group3
Group4
create subreport
put subreport under group 4 (or 3, header, footer, detail - does not
matter)
report will not run (at least for me)
if you put it inder group 1 or 2, report will work in Sept CTP 2005
package|||Great repro. I will pass it on to MS.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126879282.885405.84350@.g47g2000cwa.googlegroups.com...
> before I'll do this try to reproduce it this way:
> create report with 4 groups:
> Group1
> Group2
> Group3
> Group4
> create subreport
> put subreport under group 4 (or 3, header, footer, detail - does not
> matter)
> report will not run (at least for me)
> if you put it inder group 1 or 2, report will work in Sept CTP 2005
> package
>|||now, i think i know what really happened:
I have 4 groups
Group1
Group2
Group3
Group4
if one of the values for Group4 ( in my case Group3 also) will be null,
subreport that you will put under this group will make main report to
fail. And it happens only in Sept CTP 2005 package|||Great, I'll make sure someone gets this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126887557.215825.300160@.f14g2000cwb.googlegroups.com...
> now, i think i know what really happened:
> I have 4 groups
> Group1
> Group2
> Group3
> Group4
> if one of the values for Group4 ( in my case Group3 also) will be null,
> subreport that you will put under this group will make main report to
> fail. And it happens only in Sept CTP 2005 package
>|||hi, i have hit this same problem as well. has a fix or workaround been
identified yet?
thanks,
steve
"bosstan1@.gmail.com" wrote:
> I just installed September 2005 CTP and all reports with subreports
> getting an error:
> Error occured during local report processing. An internal error occured
> on the report server.
> If i delete subreports everything is fine. The error log says
> following:
> 09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x47405858
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0001.mdmp
> 09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x11A21E9C
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0002.mdmp
> 09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 2732
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x10B35858
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0003.mdmp
> 09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
> Any ideas?
> Everything was fine in June CTP version
>|||Has anyone found a solution to this? I am running into the same issues.
"Bruce L-C [MVP]" wrote:
> Great, I'll make sure someone gets this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <bosstan1@.gmail.com> wrote in message
> news:1126887557.215825.300160@.f14g2000cwb.googlegroups.com...
> > now, i think i know what really happened:
> > I have 4 groups
> > Group1
> > Group2
> > Group3
> > Group4
> >
> > if one of the values for Group4 ( in my case Group3 also) will be null,
> > subreport that you will put under this group will make main report to
> > fail. And it happens only in Sept CTP 2005 package
> >
>
>
Thursday, February 16, 2012
After re-installing SQL server, app did not work
For some reasons, I uninstalled and reinstalled SQL server in local pc. Now, none of my app is working. My pc is XP professional with sp2 and VS.NET is 2003.
I spent a couple of days but no luck. It drived me crazy!
Help!!!did you add the MACHINENAME/ASPNET user account to the db?|||In Web.config file, I use "sa" in connection string, do I need to add ASP.NET account?|||if you are using the useraccount "sa" to connect to the sql server then the user "sa" should have access to the database.
I spent a couple of days but no luck. It drived me crazy!
Help!!!did you add the MACHINENAME/ASPNET user account to the db?|||In Web.config file, I use "sa" in connection string, do I need to add ASP.NET account?|||if you are using the useraccount "sa" to connect to the sql server then the user "sa" should have access to the database.
After Publish from VS2005 to IIS 5.1, SQLExpress doesnt work
I created an app in vs2005 and everything works perfectly in the development environment. I've published the site to my local IIS, but when I try to log in, it doesn't allow me. I'm assuming that it has something to do with the db not working correctly. Unfortunately I don't know how to debug to see where the problem is coming from now that it's running on my 'live' IIS. Does anyone have any ideas on what could be the problem. I have some settings in the web.config, which have been working perfectly.
<appSettings>
<addkey="UserName"value=""/>
<addkey="Password"value=""/>
<addkey="Server"value="xxxxxx\sqlexpress"/>
<addkey="Database"value="xxxxx_xxx_users"/>
<addkey="UseTrusted"value="True"/>
</appSettings>
I had a local guy at the office here saying that the ASP.NET user needs to be granted access to sqlexpress2005, but I wasn't sure on how to do that.
So all in all, My app works in Visual Studio 2005, and not in IIS. There are no errors when loading various pages. They all load correctly and without error. It seems that it's just when I try to do anything with the DB.
Thanks for the help. I appreciate it!
Have you modified you connection string to point to you IIS database? Are you sure that your provider support SQL express some of them provide space on Full SQL server.
Have you moved your database together with page to new server? If yes it is possible that because ASPNET user database is encrypted with machine specific key your IIS server key will not and you have no access to database.
And it is also true that if you use windows security your ASP account have to have login associated with it on SQL Server.
I hope that it helps a little,
Thanks
|||Hey thanks for the reply.
Have you modified you connection string to point to you IIS database?
I have not modified the connection string because it is using the same database being used, thus why I don't know why this isn't working.
Are you sure that your provider support SQL express some of them provide space on Full SQL server.?
This is just on my local machine here, and yes, I'm using sqlexpress
Have you moved your database together with page to new server?
Yes, we tried it on our webserver, and the same thing happened
I am using an ASPNET 2.0 login control, but it creates an instance of my user class which authenticates the user directly from my sqlexpress db, which is used in the whole application, and then authenticates based on username and password.
I am using windows authentication.
Ok after doing a little authentication taking out, it turns out that the only thing not working is the login. All the other db queries work perfectly. It's just the login that is failing. I took a look at one of the tutorial videos and noticed that scott went into the ASP.NET Configuration page and created users and member groups there. Does that need to happen? It creates it's own database for users that's pretty locked down. I want to be able to use my own database I created.
Any ideas?
|||Are all tables working one and login in the same databse? Does you user have rights to connect to them and select from them? does it has rights to excute your stored procedures connected to login?
Thanks
|||It turns out it was the aspnet user access in sql express. I gave the user permission and all is a go now. Thanks for the help!Monday, February 13, 2012
After Install of 2005 still 2000 Engine!
I have installed the new SQL Server 2005, but I see my local database as version 8.9.193, means SQL Server 2000.
I do not know why setup did not upgrade it. What do I need to do now? I think some new options are now working because of that...
Was your SQL Server 2005 installation successful? And did you do an upgrade, or a separate instance installation? Check to see if you have a second instance of sql server running, this may be your SQL 2005 installation.|||How to check if I have second instance? How to see all my instances? Thanks
|||look at your services in control panel.|||What should I look exactly at? I see SQl Server (SQl Express) service...|||
That is probably your named instance, which you installed instead of upgraded.
http://msdn2.microsoft.com/en-us/library/ms165614.aspx
You can search msdn for more information regarding your named instance.
|||Is not that SQl Server Express 2005? I had it installed before...|||i just reread your post. where do you see "8.9.193"? if you do "select @.@.version", that will tell you the version of your sql server installation.|||Thanks. I have executed the SQL:Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
Seems I have still the old version of SQL, however I can not run Enetrprise Manager anymore, it gives me some strange errors. However it seems I can manage this instance as well as SQl Server Express instance from the new SQL Management Studio. The problem is that some options do not work (grayed out). I think the reason is that this version was not upgraded.
Can I upgrade this version without using Setup? My DVD has some scratches...|||
Hi I wonder now. Is it possible that SQL Express 2005 has been upgraded to full version, but the instance is still called SQLExpress, even it is full version SQL Server 2005?
Please let me know. Thanks
|||I have tried to copy database from SQL 2000 instance but it does not accept this destination name: h001335\SQLEXPRESS
I have checked the speeling, it is correct instance.
Any idea?
|||After ignoring the previous message I got the following:
TITLE: Copy Database Wizard
The server is SQL Server Express. This application will not work with Express Edition.
BUTTONS:
OK
Radiogeneris, please read the Books Online that came with your SQL SErver 2005 installation, it will give you a good overview as well as help you better understand your installation process/problems.
You can also access it online at http://msdn2.microsoft.com/ms165606(en-US,SQL.90).aspx.
After you've read the documentation, please feel free to post any follow up questions.
After Install of 2005 still 2000 Engine!
I have installed the new SQL Server 2005, but I see my local database as version 8.9.193, means SQL Server 2000.
I do not know why setup did not upgrade it. What do I need to do now? I think some new options are now working because of that...
Was your SQL Server 2005 installation successful? And did you do an upgrade, or a separate instance installation? Check to see if you have a second instance of sql server running, this may be your SQL 2005 installation.|||How to check if I have second instance? How to see all my instances? Thanks
|||look at your services in control panel.|||What should I look exactly at? I see SQl Server (SQl Express) service...|||
That is probably your named instance, which you installed instead of upgraded.
http://msdn2.microsoft.com/en-us/library/ms165614.aspx
You can search msdn for more information regarding your named instance.
|||Is not that SQl Server Express 2005? I had it installed before...|||i just reread your post. where do you see "8.9.193"? if you do "select @.@.version", that will tell you the version of your sql server installation.|||Thanks. I have executed the SQL:Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
Seems I have still the old version of SQL, however I can not run Enetrprise Manager anymore, it gives me some strange errors. However it seems I can manage this instance as well as SQl Server Express instance from the new SQL Management Studio. The problem is that some options do not work (grayed out). I think the reason is that this version was not upgraded.
Can I upgrade this version without using Setup? My DVD has some scratches...|||
Hi I wonder now. Is it possible that SQL Express 2005 has been upgraded to full version, but the instance is still called SQLExpress, even it is full version SQL Server 2005?
Please let me know. Thanks
|||I have tried to copy database from SQL 2000 instance but it does not accept this destination name: h001335\SQLEXPRESS
I have checked the speeling, it is correct instance.
Any idea?
|||After ignoring the previous message I got the following:
TITLE: Copy Database Wizard
The server is SQL Server Express. This application will not work with Express Edition.
BUTTONS:
OK
Radiogeneris, please read the Books Online that came with your SQL SErver 2005 installation, it will give you a good overview as well as help you better understand your installation process/problems.
You can also access it online at http://msdn2.microsoft.com/ms165606(en-US,SQL.90).aspx.
After you've read the documentation, please feel free to post any follow up questions.
After I change Log on of SQL Server 2005, my SQL service agent can not start, any idea?
I use localsystem to start SQL 2005, and use a domain/user to start SQL 2005 agent, the user is an domain admin and local admin, which works.
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well, but now, I can not start SQL 2005 agent, I get error:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
and another enry in event viewer, not sure if they are related
SQL Server blocked access to procedure 'dbo.sp_sqlagent_get_startup_info' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
It is SQL 2005 on window 2003.
Any idea how to fix it?
thanks!
In sql 2005 the agent xps are turned 'off by default' so I think the first thing you need to do is turn on the Agent Xps.
exec sp_configure 'show advanced options' , 1 ;reconfigure
exec sp_configure 'Agent XPs',1;reconfigure
go
hth,
-Steven Gott
S/DET
SQL Server
p.s. SQL 2005 does not need to run as a domain admin , It would be much safer if you set it to run as a normal user b/c the high privilleges of the service account combined with some of the xps like xp_cmdshell allow a dba who is sysadmin to manipulate your domain as the domain admin.
|||
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well ...
I suspect that your problem with using OPENROWSET had to do with permissions to access the file you were attempting to open. Since your original SQL Server account was not a domain account, you would not have been able to access domain resources, including files, with the MSSQL service. Once you changed to use the domain account that was set up for SQL Agent, the OPENROWSET worked since it could now access domain resources.
|||Hi,
I think you mixed SQL server account with SQL server agent account, I think it is SQL server account that will access the files for openrowset.
Well, I changed the account for my SQL server from local system to a domain admin, that solves the openrowset problem, but more other problem come in.
First, the Memory used by SQL keeps going up, reached 1.7G, I remember how to solve this, I need give the account "lock page in memory" permission, that solves it
Second, I got error, my CLR reports problem, it says
A .NET Framework error occurred during execution of user-defined routine or aggregate "linkclr_x_pdf_createpdf":
System.DllNotFoundException: Unable to load DLL 'ABCpdfCE6.dll': Not enough storage is available to process this command.
When the error happens, the SQL only use 170M memory, the server has 3G memory.
Really a big problem, how can I just set an account with fully localsystem permssion plus permission to access domain file? Since the localsystem worked fine except the openrowset problem.
thanks
|||My God, after caused me so much trouble, I found the openrowset may have nothing to do with the account. It only works for some time after each restart, even with local system, it works fine, it can access remote files, maybe because I set the permission to the sql server.
But the issue is it stops working after some time, someone said to set permission to temp folder, doesn't work for me yet.
Isn't that a big bug? could someone from the SQL team to shed a light here? I havn't been asking for the solution for many months.
|||Steve,
when I run this command I get
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.
It just will not let me turn it on ..... is there any other way to change the option?
thank you
mitch
|||You can try using the SQL Server Surface Area Configuration tool.
It will be in the configuration Tools folder under SQL Server
HTH,
-Steven Gott
SDE/T
SQL Server
|||Steve,
I tried this and I assume its the ole component? but I was able to fix some of the problem but it says it is not part of the sysadmin role which it is. I just dont know where to go from here.
thanks
mitch
After I change Log on of SQL Server 2005, my SQL service agent can not start, any idea?
I use localsystem to start SQL 2005, and use a domain/user to start SQL 2005 agent, the user is an domain admin and local admin, which works.
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well, but now, I can not start SQL 2005 agent, I get error:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
and another enry in event viewer, not sure if they are related
SQL Server blocked access to procedure 'dbo.sp_sqlagent_get_startup_info' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
It is SQL 2005 on window 2003.
Any idea how to fix it?
thanks!
In sql 2005 the agent xps are turned 'off by default' so I think the first thing you need to do is turn on the Agent Xps.
exec sp_configure 'show advanced options' , 1 ;reconfigure
exec sp_configure 'Agent XPs',1;reconfigure
go
hth,
-Steven Gott
S/DET
SQL Server
p.s. SQL 2005 does not need to run as a domain admin , It would be much safer if you set it to run as a normal user b/c the high privilleges of the service account combined with some of the xps like xp_cmdshell allow a dba who is sysadmin to manipulate your domain as the domain admin.
|||
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well ...
I suspect that your problem with using OPENROWSET had to do with permissions to access the file you were attempting to open. Since your original SQL Server account was not a domain account, you would not have been able to access domain resources, including files, with the MSSQL service. Once you changed to use the domain account that was set up for SQL Agent, the OPENROWSET worked since it could now access domain resources.
|||Hi,
I think you mixed SQL server account with SQL server agent account, I think it is SQL server account that will access the files for openrowset.
Well, I changed the account for my SQL server from local system to a domain admin, that solves the openrowset problem, but more other problem come in.
First, the Memory used by SQL keeps going up, reached 1.7G, I remember how to solve this, I need give the account "lock page in memory" permission, that solves it
Second, I got error, my CLR reports problem, it says
A .NET Framework error occurred during execution of user-defined routine or aggregate "linkclr_x_pdf_createpdf":
System.DllNotFoundException: Unable to load DLL 'ABCpdfCE6.dll': Not enough storage is available to process this command.
When the error happens, the SQL only use 170M memory, the server has 3G memory.
Really a big problem, how can I just set an account with fully localsystem permssion plus permission to access domain file? Since the localsystem worked fine except the openrowset problem.
thanks
|||My God, after caused me so much trouble, I found the openrowset may have nothing to do with the account. It only works for some time after each restart, even with local system, it works fine, it can access remote files, maybe because I set the permission to the sql server.
But the issue is it stops working after some time, someone said to set permission to temp folder, doesn't work for me yet.
Isn't that a big bug? could someone from the SQL team to shed a light here? I havn't been asking for the solution for many months.
|||Steve,
when I run this command I get
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.
It just will not let me turn it on ..... is there any other way to change the option?
thank you
mitch
|||You can try using the SQL Server Surface Area Configuration tool.
It will be in the configuration Tools folder under SQL Server
HTH,
-Steven Gott
SDE/T
SQL Server
|||Steve,
I tried this and I assume its the ole component? but I was able to fix some of the problem but it says it is not part of the sysadmin role which it is. I just dont know where to go from here.
thanks
mitch
Subscribe to:
Posts (Atom)