Showing posts with label working. Show all posts
Showing posts with label working. Show all posts

Friday, March 30, 2012

KPI

Hi all,

I've created a KPI and it is working correctly, however, I don't see it in the cube browser under the measures group? Where can I set the property to have it appear?

Thanks,

Mark

You can see KPI on "Browser View" mode on KPI's tab or sending an MDX query from the SQL Server Management Studio.

Francesco

|||Thanks Francesco, I do see it there. How can I get it to render via an Excel (2007) pivot table? I recall having generated one when I was using the Beta version of 2007.

Wednesday, March 28, 2012

killing SQLmail

Our SQLMail stopped working, so I tried to stop and
restart the SQLMail using xp_stopmail and xp_startmail.
it stopped quickly, but when I ran xp_startmail, it
appeared to hang. I killed the process, now it's saying
that it's "Killed/Rollback". It's been like that for a
while now. Does anyone know a way to get rid of this?
Can this cause other headaches?
Rob,
Are you using Microsoft Exchange? Is the Exchange Server available? This
can happen when Exchange disappears, or you lose connectivity to it.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Rob wrote:
> Our SQLMail stopped working, so I tried to stop and
> restart the SQLMail using xp_stopmail and xp_startmail.
> it stopped quickly, but when I ran xp_startmail, it
> appeared to hang. I killed the process, now it's saying
> that it's "Killed/Rollback". It's been like that for a
> while now. Does anyone know a way to get rid of this?
> Can this cause other headaches?
|||> This can happen when Exchange disappears
I'd question David Copperfield. ;-)
Oh, I can't wait for a more robust and independent mail platform in SQL
Server...
http://www.aspfaq.com/
(Reverse address to reply.)
|||I already tried that - that was also my first thought that is was because is
was doing it under wrong uder name, but that's not the case. I', logged in
to the server as the user that runs the SQLServer Agent service, and I can
open Outlook and get into the mailbox without any problems.
Regards
Steen
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> skrev i en meddelelse
news:OtVlLiCZEHA.2500@.TK2MSFTNGP09.phx.gbl...
> I'd question David Copperfield. ;-)
> Oh, I can't wait for a more robust and independent mail platform in SQL
> Server...
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||Steen,
Can you send mail from Outlook, logged on as the SQLAgent account?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Steen Persson wrote:
> I already tried that - that was also my first thought that is was because is
> was doing it under wrong uder name, but that's not the case. I', logged in
> to the server as the user that runs the SQLServer Agent service, and I can
> open Outlook and get into the mailbox without any problems.
> Regards
> Steen
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> skrev i en meddelelse
> news:OtVlLiCZEHA.2500@.TK2MSFTNGP09.phx.gbl...
>
>
|||...it seems like my previous reply to my problem has ended up in a wrong
thread - sorry 'bout that.
I have verified that I can send emails from Outlook. Everything seems to be
fine - I log on as the user that runs the SQL agent which is the same as the
user of the mailbox. The strange thing is that it worked fine the other day
when I installed Outlook on a few SQL servers, but now it fails with the
same error message on all of them. I'm wondering if there's something stupid
that I'm missing when I fire the xp_sendmail command.
The command I'm trying with just for the test is:
Use Master
EXEC xp_sendmail 'spe@.MyDomainName.dk', ' Test'
Shoudn't this be enough just to send an email or am I missing something?
Regards
Steen
"Mark Allison" <marka@.no.tinned.meat.mvps.org> skrev i en meddelelse
news:eFy9YYDZEHA.996@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Steen,
> Can you send mail from Outlook, logged on as the SQLAgent account?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Steen Persson wrote:
because is[vbcol=seagreen]
in[vbcol=seagreen]
can[vbcol=seagreen]

killing SQLmail

Our SQLMail stopped working, so I tried to stop and
restart the SQLMail using xp_stopmail and xp_startmail.
it stopped quickly, but when I ran xp_startmail, it
appeared to hang. I killed the process, now it's saying
that it's "Killed/Rollback". It's been like that for a
while now. Does anyone know a way to get rid of this?
Can this cause other headaches?Rob,
Are you using Microsoft Exchange? Is the Exchange Server available? This
can happen when Exchange disappears, or you lose connectivity to it.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Rob wrote:
> Our SQLMail stopped working, so I tried to stop and
> restart the SQLMail using xp_stopmail and xp_startmail.
> it stopped quickly, but when I ran xp_startmail, it
> appeared to hang. I killed the process, now it's saying
> that it's "Killed/Rollback". It's been like that for a
> while now. Does anyone know a way to get rid of this?
> Can this cause other headaches?|||> This can happen when Exchange disappears
I'd question David Copperfield. ;-)
Oh, I can't wait for a more robust and independent mail platform in SQL
Server...
http://www.aspfaq.com/
(Reverse address to reply.)|||I already tried that - that was also my first thought that is was because is
was doing it under wrong uder name, but that's not the case. I', logged in
to the server as the user that runs the SQLServer Agent service, and I can
open Outlook and get into the mailbox without any problems.
Regards
Steen
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> skrev i en meddelelse
news:OtVlLiCZEHA.2500@.TK2MSFTNGP09.phx.gbl...
> I'd question David Copperfield. ;-)
> Oh, I can't wait for a more robust and independent mail platform in SQL
> Server...
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Steen,
Can you send mail from Outlook, logged on as the SQLAgent account?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Steen Persson wrote:
> I already tried that - that was also my first thought that is was because
is
> was doing it under wrong uder name, but that's not the case. I', logged in
> to the server as the user that runs the SQLServer Agent service, and I can
> open Outlook and get into the mailbox without any problems.
> Regards
> Steen
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> skrev i en meddelels
e
> news:OtVlLiCZEHA.2500@.TK2MSFTNGP09.phx.gbl...
>
>
>|||...it seems like my previous reply to my problem has ended up in a wrong
thread - sorry 'bout that.
I have verified that I can send emails from Outlook. Everything seems to be
fine - I log on as the user that runs the SQL agent which is the same as the
user of the mailbox. The strange thing is that it worked fine the other day
when I installed Outlook on a few SQL servers, but now it fails with the
same error message on all of them. I'm wondering if there's something stupid
that I'm missing when I fire the xp_sendmail command.
The command I'm trying with just for the test is:
Use Master
EXEC xp_sendmail 'spe@.MyDomainName.dk', ' Test'
Shoudn't this be enough just to send an email or am I missing something?
Regards
Steen
"Mark Allison" <marka@.no.tinned.meat.mvps.org> skrev i en meddelelse
news:eFy9YYDZEHA.996@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Steen,
> Can you send mail from Outlook, logged on as the SQLAgent account?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Steen Persson wrote:
because is[vbcol=seagreen]
in[vbcol=seagreen]
can[vbcol=seagreen]sql

killing SQLmail

Our SQLMail stopped working, so I tried to stop and
restart the SQLMail using xp_stopmail and xp_startmail.
it stopped quickly, but when I ran xp_startmail, it
appeared to hang. I killed the process, now it's saying
that it's "Killed/Rollback". It's been like that for a
while now. Does anyone know a way to get rid of this?
Can this cause other headaches?Rob,
Are you using Microsoft Exchange? Is the Exchange Server available? This
can happen when Exchange disappears, or you lose connectivity to it.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Rob wrote:
> Our SQLMail stopped working, so I tried to stop and
> restart the SQLMail using xp_stopmail and xp_startmail.
> it stopped quickly, but when I ran xp_startmail, it
> appeared to hang. I killed the process, now it's saying
> that it's "Killed/Rollback". It's been like that for a
> while now. Does anyone know a way to get rid of this?
> Can this cause other headaches?|||> This can happen when Exchange disappears
I'd question David Copperfield. ;-)
Oh, I can't wait for a more robust and independent mail platform in SQL
Server...
--
http://www.aspfaq.com/
(Reverse address to reply.)|||I already tried that - that was also my first thought that is was because is
was doing it under wrong uder name, but that's not the case. I', logged in
to the server as the user that runs the SQLServer Agent service, and I can
open Outlook and get into the mailbox without any problems.
Regards
Steen
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> skrev i en meddelelse
news:OtVlLiCZEHA.2500@.TK2MSFTNGP09.phx.gbl...
> > This can happen when Exchange disappears
> I'd question David Copperfield. ;-)
> Oh, I can't wait for a more robust and independent mail platform in SQL
> Server...
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Steen,
Can you send mail from Outlook, logged on as the SQLAgent account?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Steen Persson wrote:
> I already tried that - that was also my first thought that is was because is
> was doing it under wrong uder name, but that's not the case. I', logged in
> to the server as the user that runs the SQLServer Agent service, and I can
> open Outlook and get into the mailbox without any problems.
> Regards
> Steen
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> skrev i en meddelelse
> news:OtVlLiCZEHA.2500@.TK2MSFTNGP09.phx.gbl...
>>This can happen when Exchange disappears
>>I'd question David Copperfield. ;-)
>>Oh, I can't wait for a more robust and independent mail platform in SQL
>>Server...
>>--
>>http://www.aspfaq.com/
>>(Reverse address to reply.)
>>
>
>|||...it seems like my previous reply to my problem has ended up in a wrong
thread - sorry 'bout that.
I have verified that I can send emails from Outlook. Everything seems to be
fine - I log on as the user that runs the SQL agent which is the same as the
user of the mailbox. The strange thing is that it worked fine the other day
when I installed Outlook on a few SQL servers, but now it fails with the
same error message on all of them. I'm wondering if there's something stupid
that I'm missing when I fire the xp_sendmail command.
The command I'm trying with just for the test is:
Use Master
EXEC xp_sendmail 'spe@.MyDomainName.dk', ' Test'
Shoudn't this be enough just to send an email or am I missing something?
Regards
Steen
"Mark Allison" <marka@.no.tinned.meat.mvps.org> skrev i en meddelelse
news:eFy9YYDZEHA.996@.TK2MSFTNGP12.phx.gbl...
> Steen,
> Can you send mail from Outlook, logged on as the SQLAgent account?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Steen Persson wrote:
> > I already tried that - that was also my first thought that is was
because is
> > was doing it under wrong uder name, but that's not the case. I', logged
in
> > to the server as the user that runs the SQLServer Agent service, and I
can
> > open Outlook and get into the mailbox without any problems.
> >
> > Regards
> > Steen
> >
> >
> > "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> skrev i en meddelelse
> > news:OtVlLiCZEHA.2500@.TK2MSFTNGP09.phx.gbl...
> >
> >>This can happen when Exchange disappears
> >>
> >>I'd question David Copperfield. ;-)
> >>
> >>Oh, I can't wait for a more robust and independent mail platform in SQL
> >>Server...
> >>
> >>--
> >>http://www.aspfaq.com/
> >>(Reverse address to reply.)
> >>
> >>
> >
> >
> >

Friday, March 23, 2012

Kill SPs then sqlserveragent stop working

We had a lot user connections with 'sleeping' mode in sysprocesses. I killed them with the status='sleeping', I realized that i might also killed some connections are not supposed to be killed.
After that, I checked event viewer, I saw 'Unable to read local eventlog (reason: The data area passed to a system call is too small).
When I restarted the sqlserveragent service, I got'Could not start SQLserverAgent Service on local computer. The service did not return an error. This could be an internal Windows error or an internal service error. If this error persists, contact your system administrator. ' and also the following message appears in Application log
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).1) Reboot your server.
2) Don't kill processes you don't know for sure are safe. NEVER kill a
process with a SPID under 50. Those are system processes and need to be
there. Sleeping processes do not harm SQL and typically take very little
memory.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Shannon" <anonymous@.discussions.microsoft.com> wrote in message
news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> We had a lot user connections with 'sleeping' mode in sysprocesses. I
killed them with the status='sleeping', I realized that i might also killed
some connections are not supposed to be killed.
> After that, I checked event viewer, I saw 'Unable to read local eventlog
(reason: The data area passed to a system call is too small). '
> When I restarted the sqlserveragent service, I got'Could not start
SQLserverAgent Service on local computer. The service did not return an
error. This could be an internal Windows error or an internal service error.
If this error persists, contact your system administrator. ' and also the
following message appears in Application log '
> 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). '
>|||If you want to kill off all your user connections, you might try a query
like this:
select 'kill '+convert(varchar(10),spid) from sysprocesses where dbid not in
(select dbid from sysdatabases where name in ('master','msdb') union all
select 0 as dbid) order by sysprocesses.spid
"Shannon" <anonymous@.discussions.microsoft.com> wrote in message
news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> We had a lot user connections with 'sleeping' mode in sysprocesses. I
killed them with the status='sleeping', I realized that i might also killed
some connections are not supposed to be killed.
> After that, I checked event viewer, I saw 'Unable to read local eventlog
(reason: The data area passed to a system call is too small). '
> When I restarted the sqlserveragent service, I got'Could not start
SQLserverAgent Service on local computer. The service did not return an
error. This could be an internal Windows error or an internal service error.
If this error persists, contact your system administrator. ' and also the
following message appears in Application log '
> 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). '
>|||Sorry, I am not recommending you try that. I accidentally hit a
key-combination that posted that note while I was composing it and still
thinking about it.
I didn't test it and the thought process was incomplete. One of the
processes killed would be your own. Well... I take that back. If you were
in master at the time, your own process would not be listed and if you were
not in master, this query couldn't resolve sysprocesses - unless it was an
SP_ stored procedure in master. Still, adding an "and spid <> @.@.spid"
clause might be a good idea.
Of course, the select statement I listed is no threat by itself, you'd have
to execute the results.
"DHatheway" <dlhatheway@.mmm.com.nospam> wrote in message
news:c5k11b$pfh$1@.tuvok3.mmm.com...
> If you want to kill off all your user connections, you might try a query
> like this:
> select 'kill '+convert(varchar(10),spid) from sysprocesses where dbid not
in
> (select dbid from sysdatabases where name in ('master','msdb') union all
> select 0 as dbid) order by sysprocesses.spid
> "Shannon" <anonymous@.discussions.microsoft.com> wrote in message
> news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> > We had a lot user connections with 'sleeping' mode in sysprocesses. I
> killed them with the status='sleeping', I realized that i might also
killed
> some connections are not supposed to be killed.
> >
> > After that, I checked event viewer, I saw 'Unable to read local eventlog
> (reason: The data area passed to a system call is too small). '
> >
> > When I restarted the sqlserveragent service, I got'Could not start
> SQLserverAgent Service on local computer. The service did not return an
> error. This could be an internal Windows error or an internal service
error.
> If this error persists, contact your system administrator. ' and also the
> following message appears in Application log '
> >
> > 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). '
> >
> >
>|||clever! <g>
"DHatheway" <dlhatheway@.mmm.com.nospam> wrote in message
news:c5k11b$pfh$1@.tuvok3.mmm.com...
> If you want to kill off all your user connections, you might try a query
> like this:
> select 'kill '+convert(varchar(10),spid) from sysprocesses where dbid not
in
> (select dbid from sysdatabases where name in ('master','msdb') union all
> select 0 as dbid) order by sysprocesses.spid
> "Shannon" <anonymous@.discussions.microsoft.com> wrote in message
> news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> > We had a lot user connections with 'sleeping' mode in sysprocesses. I
> killed them with the status='sleeping', I realized that i might also
killed
> some connections are not supposed to be killed.
> >
> > After that, I checked event viewer, I saw 'Unable to read local eventlog
> (reason: The data area passed to a system call is too small). '
> >
> > When I restarted the sqlserveragent service, I got'Could not start
> SQLserverAgent Service on local computer. The service did not return an
> error. This could be an internal Windows error or an internal service
error.
> If this error persists, contact your system administrator. ' and also the
> following message appears in Application log '
> >
> > 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). '
> >
> >
>sql

Kill SPs then sqlserveragent stop working

We had a lot user connections with 'sleeping' mode in sysprocesses. I killed them with the status='sleeping', I realized that i might also killed some connections are not supposed to be killed.
After that, I checked event viewer, I saw 'Unable to read local eventlog (reason: The data area passed to a system call is too small). '
When I restarted the sqlserveragent service, I got'Could not start SQLserverAgent Service on local computer. The service did not return an error. This could be an internal Windows error or an internal service error. If this error persists, contact your sy
stem administrator. ' and also the following message appears in Application log '
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). '
1) Reboot your server.
2) Don't kill processes you don't know for sure are safe. NEVER kill a
process with a SPID under 50. Those are system processes and need to be
there. Sleeping processes do not harm SQL and typically take very little
memory.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Shannon" <anonymous@.discussions.microsoft.com> wrote in message
news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> We had a lot user connections with 'sleeping' mode in sysprocesses. I
killed them with the status='sleeping', I realized that i might also killed
some connections are not supposed to be killed.
> After that, I checked event viewer, I saw 'Unable to read local eventlog
(reason: The data area passed to a system call is too small). '
> When I restarted the sqlserveragent service, I got'Could not start
SQLserverAgent Service on local computer. The service did not return an
error. This could be an internal Windows error or an internal service error.
If this error persists, contact your system administrator. ' and also the
following message appears in Application log '
> 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). '
>
|||If you want to kill off all your user connections, you might try a query
like this:
select 'kill '+convert(varchar(10),spid) from sysprocesses where dbid not in
(select dbid from sysdatabases where name in ('master','msdb') union all
select 0 as dbid) order by sysprocesses.spid
"Shannon" <anonymous@.discussions.microsoft.com> wrote in message
news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> We had a lot user connections with 'sleeping' mode in sysprocesses. I
killed them with the status='sleeping', I realized that i might also killed
some connections are not supposed to be killed.
> After that, I checked event viewer, I saw 'Unable to read local eventlog
(reason: The data area passed to a system call is too small). '
> When I restarted the sqlserveragent service, I got'Could not start
SQLserverAgent Service on local computer. The service did not return an
error. This could be an internal Windows error or an internal service error.
If this error persists, contact your system administrator. ' and also the
following message appears in Application log '
> 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). '
>
|||clever! <g>
"DHatheway" <dlhatheway@.mmm.com.nospam> wrote in message
news:c5k11b$pfh$1@.tuvok3.mmm.com...
> If you want to kill off all your user connections, you might try a query
> like this:
> select 'kill '+convert(varchar(10),spid) from sysprocesses where dbid not
in
> (select dbid from sysdatabases where name in ('master','msdb') union all
> select 0 as dbid) order by sysprocesses.spid
> "Shannon" <anonymous@.discussions.microsoft.com> wrote in message
> news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> killed them with the status='sleeping', I realized that i might also
killed
> some connections are not supposed to be killed.
> (reason: The data area passed to a system call is too small). '
> SQLserverAgent Service on local computer. The service did not return an
> error. This could be an internal Windows error or an internal service
error.
> If this error persists, contact your system administrator. ' and also the
> following message appears in Application log '
> to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of
the
> SysAdmin role). '
>

Kill SPs then sqlserveragent stop working

We had a lot user connections with 'sleeping' mode in sysprocesses. I killed
them with the status='sleeping', I realized that i might also killed some c
onnections are not supposed to be killed.
After that, I checked event viewer, I saw 'Unable to read local eventlog (re
ason: The data area passed to a system call is too small). '
When I restarted the sqlserveragent service, I got'Could not start SQLserver
Agent Service on local computer. The service did not return an error. This c
ould be an internal Windows error or an internal service error. If this erro
r persists, contact your sy
stem administrator. ' and also the following message appears in Application
log '
SQLServerAgent could not be started (reason: SQLServerAgent must be able to
connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the Sys
Admin role). '1) Reboot your server.
2) Don't kill processes you don't know for sure are safe. NEVER kill a
process with a SPID under 50. Those are system processes and need to be
there. Sleeping processes do not harm SQL and typically take very little
memory.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Shannon" <anonymous@.discussions.microsoft.com> wrote in message
news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> We had a lot user connections with 'sleeping' mode in sysprocesses. I
killed them with the status='sleeping', I realized that i might also killed
some connections are not supposed to be killed.
> After that, I checked event viewer, I saw 'Unable to read local eventlog
(reason: The data area passed to a system call is too small). '
> When I restarted the sqlserveragent service, I got'Could not start
SQLserverAgent Service on local computer. The service did not return an
error. This could be an internal Windows error or an internal service error.
If this error persists, contact your system administrator. ' and also the
following message appears in Application log '
> 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). '
>|||If you want to kill off all your user connections, you might try a query
like this:
select 'kill '+convert(varchar(10),spid) from sysprocesses where dbid not in
(select dbid from sysdatabases where name in ('master','msdb') union all
select 0 as dbid) order by sysprocesses.spid
"Shannon" <anonymous@.discussions.microsoft.com> wrote in message
news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> We had a lot user connections with 'sleeping' mode in sysprocesses. I
killed them with the status='sleeping', I realized that i might also killed
some connections are not supposed to be killed.
> After that, I checked event viewer, I saw 'Unable to read local eventlog
(reason: The data area passed to a system call is too small). '
> When I restarted the sqlserveragent service, I got'Could not start
SQLserverAgent Service on local computer. The service did not return an
error. This could be an internal Windows error or an internal service error.
If this error persists, contact your system administrator. ' and also the
following message appears in Application log '
> 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). '
>|||clever! <g>
"DHatheway" <dlhatheway@.mmm.com.nospam> wrote in message
news:c5k11b$pfh$1@.tuvok3.mmm.com...
> If you want to kill off all your user connections, you might try a query
> like this:
> select 'kill '+convert(varchar(10),spid) from sysprocesses where dbid not
in
> (select dbid from sysdatabases where name in ('master','msdb') union all
> select 0 as dbid) order by sysprocesses.spid
> "Shannon" <anonymous@.discussions.microsoft.com> wrote in message
> news:128716F6-4D97-41E6-B8E6-EC001502D843@.microsoft.com...
> killed them with the status='sleeping', I realized that i might also
killed
> some connections are not supposed to be killed.
> (reason: The data area passed to a system call is too small). '
> SQLserverAgent Service on local computer. The service did not return an
> error. This could be an internal Windows error or an internal service
error.
> If this error persists, contact your system administrator. ' and also the
> following message appears in Application log '
> to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of
the
> SysAdmin role). '
>

Kill process is not working

Trying to kill a process which is causing the following
error in the log every 10 minutes.
Time out occurred while waiting for buffer latch type 2,
bp 0x144e5000, page (5120:811953513), stat 0x405, object
ID 10:1:0, waittime 3500. Continuing to wait.
How can I kill this process?Hi,
Look into the below link:-
Q310834 PRB: Common Causes of Error Message 844 or Error Message 845
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q310834
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:294bc01c465c7$a5ac5b50$a601280a@.phx.gbl...
> Trying to kill a process which is causing the following
> error in the log every 10 minutes.
> Time out occurred while waiting for buffer latch type 2,
> bp 0x144e5000, page (5120:811953513), stat 0x405, object
> ID 10:1:0, waittime 3500. Continuing to wait.
> How can I kill this process?

Kill process is not working

Trying to kill a process which is causing the following
error in the log every 10 minutes.
Time out occurred while waiting for buffer latch type 2,
bp 0x144e5000, page (5120:811953513), stat 0x405, object
ID 10:1:0, waittime 3500. Continuing to wait.
How can I kill this process?
Hi,
Look into the below link:-
Q310834 PRB: Common Causes of Error Message 844 or Error Message 845
http://support.microsoft.com/default...;EN-US;Q310834
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:294bc01c465c7$a5ac5b50$a601280a@.phx.gbl...
> Trying to kill a process which is causing the following
> error in the log every 10 minutes.
> Time out occurred while waiting for buffer latch type 2,
> bp 0x144e5000, page (5120:811953513), stat 0x405, object
> ID 10:1:0, waittime 3500. Continuing to wait.
> How can I kill this process?

Monday, March 19, 2012

Keyboard not working (backspace and arrow keys) when viewing 2000 DTS packages from 2005 (ba

I know my problem is not directly associated w/ SSIS, so please forgive the post here. I figured this would be the "most" appropriate place to post this challenge.

We're attempting to edit a 2000 DTS package in Design mode from within the 2005 SQL Management Studio. To do this we downloaded/installed the following packages from the MS download site:

Microsoft SQL Server 2000 DTS Designer Components
Microsoft SQL Server 2005 Backward Compatibility Components

We're able to open the package in design mode from the Management Studio (Server > Management > Legacy > Data Transformation Services > DTS Package Name). But, when the DTS designer is open, the backspace and arrow keys won't respond in the Management Studio. They begin responding when we close the DTS designer. There are no error messages when we close the DTS designer.

Does anyone know of a fix or a workaround? Any help would be greatly appreciated.

Thanks, Mike

Do you have the Logitech MX5000 BlueTooth keyboard/mouse? I encountered this problem just yesterday and assumed it was my bluetooth connection going in and out.

That is very strange...

|||Nope, I have a wired Compaq keyboard. My colleague has the same problem w/ a different brand of wired keyboard.|||If you do a search there are a lot of people that have had problems with this component. It hosed enterprised manager on my machine and one of my co-workers. Even when it installed correctly a bunch of us still got errors opening packages. So far the only solution I've heard is to grin and bear it.|||

Thanks for the feedback, this was identified as a bug and was fixed. The fix will be in the next release after SP1

wenyang

|||

Is this fix out yet?

|||

I saw a reference to this recently which indicated it was fixed in SP2, or the associated feature pack. That is currently released as a CTP, so you may wish to risk it. I cannot find the source niow, which is rather annoying...

Download details: Feature Pack for SQL Server 2005 SP2 CTP
(http://www.microsoft.com/downloads/details.aspx?FamilyID=7A9AD90F-7F95-4369-A206-E84053D63FD3&displaylang=en)

|||

Thanks,

but unfortunately, the same behavior is happening with the CTP version of the dts designer :(

key/value pair table update query

I'm working with a table that I've created called Config which contains key/value pairs used to get and set site-wide settings. I'm now trying to create a web form which updates the table but I'm not sure how to create the most effective UPDATE query.

Table of course takes this form key | value
----------
config_setting1 | value1
config_setting2 | value2

I'm working with a System.Collections.Specialized.StringDictionary Class object which contains all of the pairs from my webform... anybody have a creative way to build an UPDATE string using this object?

Thanks for any help and suggestions,
ecolner@.yahoo.comI suggest you to create static method to your database class that updates the configuration. The idea is simple.

1) Create parameterized SqlCommand for updates (update conf set value=@.value where setting=@.setting).
2) Start database transaction.
3) Iterate through you string dictionary and on every turn evaluate @.value and @.setting parameters again and then execute the command.
4) If there is errors then roll back database changes, otherwise commit the changes
5) Dispose the update command

Monday, March 12, 2012

Key not valid for use in specified state?

Hi!
I just ran into the same old problem that I got a few months back.
Reporting Server stops working and logs the message "Key not valid for use
in specified state".
I did never manage to solve the problem when it occured before but at that
time it happened on a development server, this time it is worse as it is
on one of our production servers.
I know that there was several people suffering from the same problem after
applying .Net Framework 1.1 SP1.
Did anyone find a solution?
Best regards,
Per SalmiHello Per,
Based on my research, I recommend you perform the following steps to
resolve the issue:
Step 1: Deleting the files which represent Microsoft SQL Server Reporting
Services Key Container
===============================================================
Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
These files represent the Microsoft SQL Server Reporting Services Key
Container.
Backup these files first. Then delete the original files.
You may find the file in the folder "\documents and settings\<machine
name>\aspnet\application data\microsoft\crypto\rsa\<user
sid>\1aedd7b5699f3d6a88e354100b596aae_*".
Try to start Reporting Server.
If you receive "The report server cannot decrypt the symmetric key used to
access sensitive or encrypted data in a report server database. You must
either restore a backup key or delete all encrypted content and then
restart the service. Check the documentation", please continue with the
following steps:
Step 2: Back up Reportserver and ReportserverTempDB databases
===========================================
Step 3: Reapplying the symmetric keys
==================================
1. Run Rskeymgmt -e to extract the keys
2. Run Rskeymgmt -d to delete the keys
3. Run rskeymgmt -a to reapply the keys and restart the windows service.
4. Run Rsactivate -c to activate the service
For detailed information about the RsKeyMgmt utility, please access the
following web site:
http://www.msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref
/htm/cpu_rsconfig_v1_29ly.asp
I hope above information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Key not valid for use in specified state

Hi!
On thursday last week one of our clients Reporting Services installation
stopped working and reports "Key not valid for use in specified state" error
message in the log files.
This is strange as we have not done any changes to the server. It is running
Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
Anyone got similar problems or know what could cause this behaviour?
I have tried reinstalling the encryption keys and finally removing and
reinstalling the complete Reporting Services but the same error is logged
and the service doesn't work.
Best regards,
Per SalmiI am getting exactly the same problem, also in Win2k3, and have also done a
complete uninstall and reinstall of RS, to no avail.
Surely someone in Microsoft can resolve this'? I have had to abandon work
because of this error.
brian smith
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> Hi!
> On thursday last week one of our clients Reporting Services installation
> stopped working and reports "Key not valid for use in specified state"
error
> message in the log files.
> This is strange as we have not done any changes to the server. It is
running
> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> Anyone got similar problems or know what could cause this behaviour?
> I have tried reinstalling the encryption keys and finally removing and
> reinstalling the complete Reporting Services but the same error is logged
> and the service doesn't work.
> Best regards,
> Per Salmi
>|||I have found one thing that differs between two servers we have one where RS
works perfectly and the one mentioned with the "key problem". The difference
is that the server that doesn't work has an SQL instance that was upgraded
from SQL7 but the one that works is running on a clean installed SQL2K
instance.
The OS is W2K3 on both servers.
On the one that now suffers from the problem I also had problems where the
Report Manager web application would not install/configure correctly during
install. Never got the manager to work so I used another machine for the web
application.
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>I am getting exactly the same problem, also in Win2k3, and have also done a
> complete uninstall and reinstall of RS, to no avail.
> Surely someone in Microsoft can resolve this'? I have had to abandon
> work
> because of this error.
> brian smith
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> Hi!
>> On thursday last week one of our clients Reporting Services installation
>> stopped working and reports "Key not valid for use in specified state"
> error
>> message in the log files.
>> This is strange as we have not done any changes to the server. It is
> running
>> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> Anyone got similar problems or know what could cause this behaviour?
>> I have tried reinstalling the encryption keys and finally removing and
>> reinstalling the complete Reporting Services but the same error is logged
>> and the service doesn't work.
>> Best regards,
>> Per Salmi
>>
>|||I don't think the SQL7 upgrade is relevant - my server was a clean install
with SQL 2000. I have followed 2 possible causes on my system:
1 - the .Net Framework 1.1 SP1 update (although RS did continue for a week
or so)
2 - the fact that I originally installed the 120 day trial version of RS,
before updating it a few weeks later.
After a clean removal, including the databases, and reinstall, plus RS SP1
I'm no better off. This looks like a bug, which worries me greatly as I have
customers dependant on the product and I fear this error will suddenly occur
on their system too.
Brian
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> I have found one thing that differs between two servers we have one where
RS
> works perfectly and the one mentioned with the "key problem". The
difference
> is that the server that doesn't work has an SQL instance that was upgraded
> from SQL7 but the one that works is running on a clean installed SQL2K
> instance.
> The OS is W2K3 on both servers.
> On the one that now suffers from the problem I also had problems where the
> Report Manager web application would not install/configure correctly
during
> install. Never got the manager to work so I used another machine for the
web
> application.
> /Per Salmi
> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> >I am getting exactly the same problem, also in Win2k3, and have also done
a
> > complete uninstall and reinstall of RS, to no avail.
> > Surely someone in Microsoft can resolve this'? I have had to abandon
> > work
> > because of this error.
> >
> > brian smith
> >
> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> >> Hi!
> >>
> >> On thursday last week one of our clients Reporting Services
installation
> >> stopped working and reports "Key not valid for use in specified state"
> > error
> >> message in the log files.
> >>
> >> This is strange as we have not done any changes to the server. It is
> > running
> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> >>
> >> Anyone got similar problems or know what could cause this behaviour?
> >>
> >> I have tried reinstalling the encryption keys and finally removing and
> >> reinstalling the complete Reporting Services but the same error is
logged
> >> and the service doesn't work.
> >>
> >> Best regards,
> >> Per Salmi
> >>
> >>
> >
> >
>|||To follow on from my earlier messaege - the error appears to relate to
something to do with encryption. I know nothing about encryption, or why it
is involved in RS, but I assume it involves licensing.
These are lines in the RS log:
aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto as
user: DRAKE\ASPNET
aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public key
aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
System.Runtime.InteropServices.COMException (0x8009000B): Key not valid for
use in specified state.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ExportPublicKey()
at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
Brian
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> I have found one thing that differs between two servers we have one where
RS
> works perfectly and the one mentioned with the "key problem". The
difference
> is that the server that doesn't work has an SQL instance that was upgraded
> from SQL7 but the one that works is running on a clean installed SQL2K
> instance.
> The OS is W2K3 on both servers.
> On the one that now suffers from the problem I also had problems where the
> Report Manager web application would not install/configure correctly
during
> install. Never got the manager to work so I used another machine for the
web
> application.
> /Per Salmi
> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> >I am getting exactly the same problem, also in Win2k3, and have also done
a
> > complete uninstall and reinstall of RS, to no avail.
> > Surely someone in Microsoft can resolve this'? I have had to abandon
> > work
> > because of this error.
> >
> > brian smith
> >
> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> >> Hi!
> >>
> >> On thursday last week one of our clients Reporting Services
installation
> >> stopped working and reports "Key not valid for use in specified state"
> > error
> >> message in the log files.
> >>
> >> This is strange as we have not done any changes to the server. It is
> > running
> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> >>
> >> Anyone got similar problems or know what could cause this behaviour?
> >>
> >> I have tried reinstalling the encryption keys and finally removing and
> >> reinstalling the complete Reporting Services but the same error is
logged
> >> and the service doesn't work.
> >>
> >> Best regards,
> >> Per Salmi
> >>
> >>
> >
> >
>|||Ok, I did never install any evaluation version of RS on this server. This
actually happened on aserver used in full production. But I moved the
reporting stuff to the other server. I am afraid that it will break on that
server too.
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:%237KuxYjoEHA.2912@.TK2MSFTNGP10.phx.gbl...
>I don't think the SQL7 upgrade is relevant - my server was a clean install
> with SQL 2000. I have followed 2 possible causes on my system:
> 1 - the .Net Framework 1.1 SP1 update (although RS did continue for a week
> or so)
> 2 - the fact that I originally installed the 120 day trial version of RS,
> before updating it a few weeks later.
> After a clean removal, including the databases, and reinstall, plus RS SP1
> I'm no better off. This looks like a bug, which worries me greatly as I
> have
> customers dependant on the product and I fear this error will suddenly
> occur
> on their system too.
> Brian
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
>> I have found one thing that differs between two servers we have one where
> RS
>> works perfectly and the one mentioned with the "key problem". The
> difference
>> is that the server that doesn't work has an SQL instance that was
>> upgraded
>> from SQL7 but the one that works is running on a clean installed SQL2K
>> instance.
>> The OS is W2K3 on both servers.
>> On the one that now suffers from the problem I also had problems where
>> the
>> Report Manager web application would not install/configure correctly
> during
>> install. Never got the manager to work so I used another machine for the
> web
>> application.
>> /Per Salmi
>> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
>> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>> >I am getting exactly the same problem, also in Win2k3, and have also
>> >done
> a
>> > complete uninstall and reinstall of RS, to no avail.
>> > Surely someone in Microsoft can resolve this'? I have had to abandon
>> > work
>> > because of this error.
>> >
>> > brian smith
>> >
>> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
>> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> >> Hi!
>> >>
>> >> On thursday last week one of our clients Reporting Services
> installation
>> >> stopped working and reports "Key not valid for use in specified state"
>> > error
>> >> message in the log files.
>> >>
>> >> This is strange as we have not done any changes to the server. It is
>> > running
>> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> >>
>> >> Anyone got similar problems or know what could cause this behaviour?
>> >>
>> >> I have tried reinstalling the encryption keys and finally removing and
>> >> reinstalling the complete Reporting Services but the same error is
> logged
>> >> and the service doesn't work.
>> >>
>> >> Best regards,
>> >> Per Salmi
>> >>
>> >>
>> >
>> >
>>
>|||Seems like exactly the same error I get.
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:eIYFOhjoEHA.3424@.TK2MSFTNGP12.phx.gbl...
> To follow on from my earlier messaege - the error appears to relate to
> something to do with encryption. I know nothing about encryption, or why
> it
> is involved in RS, but I assume it involves licensing.
> These are lines in the RS log:
> aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto as
> user: DRAKE\ASPNET
> aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public key
> aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
> System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> for
> use in specified state.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSManagedCrypto.RSCrypto.ExportPublicKey()
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
>
> Brian
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
>> I have found one thing that differs between two servers we have one where
> RS
>> works perfectly and the one mentioned with the "key problem". The
> difference
>> is that the server that doesn't work has an SQL instance that was
>> upgraded
>> from SQL7 but the one that works is running on a clean installed SQL2K
>> instance.
>> The OS is W2K3 on both servers.
>> On the one that now suffers from the problem I also had problems where
>> the
>> Report Manager web application would not install/configure correctly
> during
>> install. Never got the manager to work so I used another machine for the
> web
>> application.
>> /Per Salmi
>> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
>> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>> >I am getting exactly the same problem, also in Win2k3, and have also
>> >done
> a
>> > complete uninstall and reinstall of RS, to no avail.
>> > Surely someone in Microsoft can resolve this'? I have had to abandon
>> > work
>> > because of this error.
>> >
>> > brian smith
>> >
>> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
>> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> >> Hi!
>> >>
>> >> On thursday last week one of our clients Reporting Services
> installation
>> >> stopped working and reports "Key not valid for use in specified state"
>> > error
>> >> message in the log files.
>> >>
>> >> This is strange as we have not done any changes to the server. It is
>> > running
>> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> >>
>> >> Anyone got similar problems or know what could cause this behaviour?
>> >>
>> >> I have tried reinstalling the encryption keys and finally removing and
>> >> reinstalling the complete Reporting Services but the same error is
> logged
>> >> and the service doesn't work.
>> >>
>> >> Best regards,
>> >> Per Salmi
>> >>
>> >>
>> >
>> >
>>
>|||Actually I find that the .NET FW 1.1 SP1 is not installed on the server
where RS continues to work...
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:%237KuxYjoEHA.2912@.TK2MSFTNGP10.phx.gbl...
>I don't think the SQL7 upgrade is relevant - my server was a clean install
> with SQL 2000. I have followed 2 possible causes on my system:
> 1 - the .Net Framework 1.1 SP1 update (although RS did continue for a week
> or so)
> 2 - the fact that I originally installed the 120 day trial version of RS,
> before updating it a few weeks later.
> After a clean removal, including the databases, and reinstall, plus RS SP1
> I'm no better off. This looks like a bug, which worries me greatly as I
> have
> customers dependant on the product and I fear this error will suddenly
> occur
> on their system too.
> Brian
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
>> I have found one thing that differs between two servers we have one where
> RS
>> works perfectly and the one mentioned with the "key problem". The
> difference
>> is that the server that doesn't work has an SQL instance that was
>> upgraded
>> from SQL7 but the one that works is running on a clean installed SQL2K
>> instance.
>> The OS is W2K3 on both servers.
>> On the one that now suffers from the problem I also had problems where
>> the
>> Report Manager web application would not install/configure correctly
> during
>> install. Never got the manager to work so I used another machine for the
> web
>> application.
>> /Per Salmi
>> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
>> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>> >I am getting exactly the same problem, also in Win2k3, and have also
>> >done
> a
>> > complete uninstall and reinstall of RS, to no avail.
>> > Surely someone in Microsoft can resolve this'? I have had to abandon
>> > work
>> > because of this error.
>> >
>> > brian smith
>> >
>> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
>> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> >> Hi!
>> >>
>> >> On thursday last week one of our clients Reporting Services
> installation
>> >> stopped working and reports "Key not valid for use in specified state"
>> > error
>> >> message in the log files.
>> >>
>> >> This is strange as we have not done any changes to the server. It is
>> > running
>> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> >>
>> >> Anyone got similar problems or know what could cause this behaviour?
>> >>
>> >> I have tried reinstalling the encryption keys and finally removing and
>> >> reinstalling the complete Reporting Services but the same error is
> logged
>> >> and the service doesn't work.
>> >>
>> >> Best regards,
>> >> Per Salmi
>> >>
>> >>
>> >
>> >
>>
>|||Has anyone found the actual cause of this error? I do not want to
have to re-install RServices on a regular basis.
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message news:<eU5aTJkoEHA.1664@.tk2msftngp13.phx.gbl>...
> Seems like exactly the same error I get.
> /Per Salmi
> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> news:eIYFOhjoEHA.3424@.TK2MSFTNGP12.phx.gbl...
> > To follow on from my earlier messaege - the error appears to relate to
> > something to do with encryption. I know nothing about encryption, or why
> > it
> > is involved in RS, but I assume it involves licensing.
> >
> > These are lines in the RS log:
> > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto as
> > user: DRAKE\ASPNET
> > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public key
> > aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > for
> > use in specified state.
> > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> > errorCode, IntPtr errorInfo)
> > at RSManagedCrypto.RSCrypto.ExportPublicKey()
> > at
> > Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> >
> >
> > Brian
> >
> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> >> I have found one thing that differs between two servers we have one where
> RS
> >> works perfectly and the one mentioned with the "key problem". The
> difference
> >> is that the server that doesn't work has an SQL instance that was
> >> upgraded
> >> from SQL7 but the one that works is running on a clean installed SQL2K
> >> instance.
> >>
> >> The OS is W2K3 on both servers.
> >>
> >> On the one that now suffers from the problem I also had problems where
> >> the
> >> Report Manager web application would not install/configure correctly
> during
> >> install. Never got the manager to work so I used another machine for the
> web
> >> application.
> >>
> >> /Per Salmi
> >>
> >> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> >> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> >> >I am getting exactly the same problem, also in Win2k3, and have also
> >> >done
> a
> >> > complete uninstall and reinstall of RS, to no avail.
> >> > Surely someone in Microsoft can resolve this'? I have had to abandon
> >> > work
> >> > because of this error.
> >> >
> >> > brian smith
> >> >
> >> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> >> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> >> >> Hi!
> >> >>
> >> >> On thursday last week one of our clients Reporting Services
> installation
> >> >> stopped working and reports "Key not valid for use in specified state"
> error
> >> >> message in the log files.
> >> >>
> >> >> This is strange as we have not done any changes to the server. It is
> running
> >> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> >> >>
> >> >> Anyone got similar problems or know what could cause this behaviour?
> >> >>
> >> >> I have tried reinstalling the encryption keys and finally removing and
> >> >> reinstalling the complete Reporting Services but the same error is
> logged
> >> >> and the service doesn't work.
> >> >>
> >> >> Best regards,
> >> >> Per Salmi
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >|||I have an ongoing (paid) support case with MS, but so far despite all the
suggestions, my RS still does not work. When (and if) they fix it, I'll post
an update.
brian
"Austin S" <austinswope@.gmail.com> wrote in message
news:b68c96f7.0410180951.57c3121e@.posting.google.com...
> Has anyone found the actual cause of this error? I do not want to
> have to re-install RServices on a regular basis.
>
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:<eU5aTJkoEHA.1664@.tk2msftngp13.phx.gbl>...
> > Seems like exactly the same error I get.
> >
> > /Per Salmi
> >
> > "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> > news:eIYFOhjoEHA.3424@.TK2MSFTNGP12.phx.gbl...
> > > To follow on from my earlier messaege - the error appears to relate to
> > > something to do with encryption. I know nothing about encryption, or
why
> > > it
> > > is involved in RS, but I assume it involves licensing.
> > >
> > > These are lines in the RS log:
> > > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto
as
> > > user: DRAKE\ASPNET
> > > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public
key
> > > aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
> > > System.Runtime.InteropServices.COMException (0x8009000B): Key not
valid
> > > for
> > > use in specified state.
> > > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> > > errorCode, IntPtr errorInfo)
> > > at RSManagedCrypto.RSCrypto.ExportPublicKey()
> > > at
> > >
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > >
> > >
> > > Brian
> > >
> > > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > > news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> > >> I have found one thing that differs between two servers we have one
where
> > RS
> > >> works perfectly and the one mentioned with the "key problem". The
> > difference
> > >> is that the server that doesn't work has an SQL instance that was
> > >> upgraded
> > >> from SQL7 but the one that works is running on a clean installed
SQL2K
> > >> instance.
> > >>
> > >> The OS is W2K3 on both servers.
> > >>
> > >> On the one that now suffers from the problem I also had problems
where
> > >> the
> > >> Report Manager web application would not install/configure correctly
> > during
> > >> install. Never got the manager to work so I used another machine for
the
> > web
> > >> application.
> > >>
> > >> /Per Salmi
> > >>
> > >> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> > >> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> > >> >I am getting exactly the same problem, also in Win2k3, and have also
> > >> >done
> > a
> > >> > complete uninstall and reinstall of RS, to no avail.
> > >> > Surely someone in Microsoft can resolve this'? I have had to
abandon
> > >> > work
> > >> > because of this error.
> > >> >
> > >> > brian smith
> > >> >
> > >> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > >> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> > >> >> Hi!
> > >> >>
> > >> >> On thursday last week one of our clients Reporting Services
> > installation
> > >> >> stopped working and reports "Key not valid for use in specified
state"
> > error
> > >> >> message in the log files.
> > >> >>
> > >> >> This is strange as we have not done any changes to the server. It
is
> > running
> > >> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> > >> >>
> > >> >> Anyone got similar problems or know what could cause this
behaviour?
> > >> >>
> > >> >> I have tried reinstalling the encryption keys and finally removing
and
> > >> >> reinstalling the complete Reporting Services but the same error is
> > logged
> > >> >> and the service doesn't work.
> > >> >>
> > >> >> Best regards,
> > >> >> Per Salmi
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >|||I'd love to hear the solution too - I just ran into this exact error after
.Net Framework 1.1 SP1 was installed over the weekend.
I've tried the other solutions in these threads, but nothing has worked.
Dave
"Brian Smith" wrote:
> I have an ongoing (paid) support case with MS, but so far despite all the
> suggestions, my RS still does not work. When (and if) they fix it, I'll post
> an update.
> brian
>

Friday, March 9, 2012

Kerberos delegation in extranet scenario

Anyone gotten Kerberos delegation working in an extranet scenario?

We've followed the instructions outlined here:

http://support.microsoft.com/default.aspx/kb/917409

http://www.mosha.com/msolap/articles/kerberos_delegation.htm

Kerberos delegation is working as long as the user's browser has the website in the Intranet Zone (so that it automatically logs them on). If the website is not in the Intranet Zone, it prompts them to type in their Active Directory credentials, they're able to connect with the website fine once they've entered their credentials, but then Kerberos delegation doesn't succeed.

I don't want to get into detail in troubleshooting Kerberos tickets in this forum. Just wondering if anybody else has run across this problem and found a fix/workaround.

For internal users, we can ensure the website is in the Intranet Zone. This won't work for external users (a) because they have logged onto their laptop with credentials from a different domain and (b) we can't control their IE browser settings.

Hello! If you are talking about reports build on top of SSAS2005 this issue can be related to NTFS(file system) issues.

If you build a report in a client tool and save it to disk you will have prompts for user credentails for outsiders.

If you build a report with a HTTP connection to SSAS2005 with a third party tool it can work.

Kerberos is for authenticating users between two servers?

Regards

Thomas Ivarsson

|||

Thomas-

Kerberos delegation is needed is so that we can put SSAS on a separate server than our web server. There will be several web servers. One for SSRS and one for PerformancePoint. Both web servers need to support passing through the authenticated user's credentials all the way to the cube (so that cube security will work as designed).

The testing we've done thus far is with SSRS as the web server and a report that hits the cube using the authenticated user's credentials. That's the scenario I described above where we're seeing the Intranet Zone thing.

Can you elaborate on the NTFS file system issues or provide a link?

Users don't need to connect directly to SSAS (just through a SSRS or PP) so I'm thinking we don't need to turn on HTTP connectivity for SSAS. But if that helps workaround kerberos restrictions or something, let me know.

Thanks for the reply.

|||

Furmangg:

I have read your post once again:

All external users have an account in AD?

Quote:

"This won't work for external users (a) because they have logged onto their laptop with credentials from a different domain and (b) we can't control their IE browser settings"

It is about IE settings? You have a setting like "Allow database connections across domains" . This is disabled in IE7.

HTH

Thomas Ivarsson

|||

Thomas-

Yes, external users will have an account in our company's AD in this particular deployment. But they don't sign into their laptop with our company's AD... they sign into their laptop under their company's AD... then when they pull up our extranet, they're prompted to login as someone in our company's AD. And that, from what I've read, won't allow Kerberos.

As for the "Allow database connections across domains" setting in IE, I don't think that applies. We're talking about thin-client web apps. If I understood that setting correctly, it's for thicker client web apps which are doing fancy stuff like databinding inside the webpage with ActiveX or something: http://www.microsoft.com/technet/prodtechnol/ie/ieak/techinfo/deploy/60/en/secopt.mspx?mfr=true

|||

I got some help from a number of smart people and the following two options look promising:

1. ISA 2006

http://www.microsoft.com/technet/isa/2006/authentication.mspx

2. Protocol Transition

http://justpickanything.adopenstatic.com/cs/blogs/ken/archive/2007/07/18/8460.aspx

Just wanted to give everyone an update.

Kerberos delegation in extranet scenario

Anyone gotten Kerberos delegation working in an extranet scenario?

We've followed the instructions outlined here:

http://support.microsoft.com/default.aspx/kb/917409

http://www.mosha.com/msolap/articles/kerberos_delegation.htm

Kerberos delegation is working as long as the user's browser has the website in the Intranet Zone (so that it automatically logs them on). If the website is not in the Intranet Zone, it prompts them to type in their Active Directory credentials, they're able to connect with the website fine once they've entered their credentials, but then Kerberos delegation doesn't succeed.

I don't want to get into detail in troubleshooting Kerberos tickets in this forum. Just wondering if anybody else has run across this problem and found a fix/workaround.

For internal users, we can ensure the website is in the Intranet Zone. This won't work for external users (a) because they have logged onto their laptop with credentials from a different domain and (b) we can't control their IE browser settings.

Hello! If you are talking about reports build on top of SSAS2005 this issue can be related to NTFS(file system) issues.

If you build a report in a client tool and save it to disk you will have prompts for user credentails for outsiders.

If you build a report with a HTTP connection to SSAS2005 with a third party tool it can work.

Kerberos is for authenticating users between two servers?

Regards

Thomas Ivarsson

|||

Thomas-

Kerberos delegation is needed is so that we can put SSAS on a separate server than our web server. There will be several web servers. One for SSRS and one for PerformancePoint. Both web servers need to support passing through the authenticated user's credentials all the way to the cube (so that cube security will work as designed).

The testing we've done thus far is with SSRS as the web server and a report that hits the cube using the authenticated user's credentials. That's the scenario I described above where we're seeing the Intranet Zone thing.

Can you elaborate on the NTFS file system issues or provide a link?

Users don't need to connect directly to SSAS (just through a SSRS or PP) so I'm thinking we don't need to turn on HTTP connectivity for SSAS. But if that helps workaround kerberos restrictions or something, let me know.

Thanks for the reply.

|||

Furmangg:

I have read your post once again:

All external users have an account in AD?

Quote:

"This won't work for external users (a) because they have logged onto their laptop with credentials from a different domain and (b) we can't control their IE browser settings"

It is about IE settings? You have a setting like "Allow database connections across domains" . This is disabled in IE7.

HTH

Thomas Ivarsson

|||

Thomas-

Yes, external users will have an account in our company's AD in this particular deployment. But they don't sign into their laptop with our company's AD... they sign into their laptop under their company's AD... then when they pull up our extranet, they're prompted to login as someone in our company's AD. And that, from what I've read, won't allow Kerberos.

As for the "Allow database connections across domains" setting in IE, I don't think that applies. We're talking about thin-client web apps. If I understood that setting correctly, it's for thicker client web apps which are doing fancy stuff like databinding inside the webpage with ActiveX or something: http://www.microsoft.com/technet/prodtechnol/ie/ieak/techinfo/deploy/60/en/secopt.mspx?mfr=true

|||

I got some help from a number of smart people and the following two options look promising:

1. ISA 2006

http://www.microsoft.com/technet/isa/2006/authentication.mspx

2. Protocol Transition

http://justpickanything.adopenstatic.com/cs/blogs/ken/archive/2007/07/18/8460.aspx

Just wanted to give everyone an update.

Kerberos delegation in extranet scenario

Anyone gotten Kerberos delegation working in an extranet scenario?

We've followed the instructions outlined here:

http://support.microsoft.com/default.aspx/kb/917409

http://www.mosha.com/msolap/articles/kerberos_delegation.htm

Kerberos delegation is working as long as the user's browser has the website in the Intranet Zone (so that it automatically logs them on). If the website is not in the Intranet Zone, it prompts them to type in their Active Directory credentials, they're able to connect with the website fine once they've entered their credentials, but then Kerberos delegation doesn't succeed.

I don't want to get into detail in troubleshooting Kerberos tickets in this forum. Just wondering if anybody else has run across this problem and found a fix/workaround.

For internal users, we can ensure the website is in the Intranet Zone. This won't work for external users (a) because they have logged onto their laptop with credentials from a different domain and (b) we can't control their IE browser settings.

Hello! If you are talking about reports build on top of SSAS2005 this issue can be related to NTFS(file system) issues.

If you build a report in a client tool and save it to disk you will have prompts for user credentails for outsiders.

If you build a report with a HTTP connection to SSAS2005 with a third party tool it can work.

Kerberos is for authenticating users between two servers?

Regards

Thomas Ivarsson

|||

Thomas-

Kerberos delegation is needed is so that we can put SSAS on a separate server than our web server. There will be several web servers. One for SSRS and one for PerformancePoint. Both web servers need to support passing through the authenticated user's credentials all the way to the cube (so that cube security will work as designed).

The testing we've done thus far is with SSRS as the web server and a report that hits the cube using the authenticated user's credentials. That's the scenario I described above where we're seeing the Intranet Zone thing.

Can you elaborate on the NTFS file system issues or provide a link?

Users don't need to connect directly to SSAS (just through a SSRS or PP) so I'm thinking we don't need to turn on HTTP connectivity for SSAS. But if that helps workaround kerberos restrictions or something, let me know.

Thanks for the reply.

|||

Furmangg:

I have read your post once again:

All external users have an account in AD?

Quote:

"This won't work for external users (a) because they have logged onto their laptop with credentials from a different domain and (b) we can't control their IE browser settings"

It is about IE settings? You have a setting like "Allow database connections across domains" . This is disabled in IE7.

HTH

Thomas Ivarsson

|||

Thomas-

Yes, external users will have an account in our company's AD in this particular deployment. But they don't sign into their laptop with our company's AD... they sign into their laptop under their company's AD... then when they pull up our extranet, they're prompted to login as someone in our company's AD. And that, from what I've read, won't allow Kerberos.

As for the "Allow database connections across domains" setting in IE, I don't think that applies. We're talking about thin-client web apps. If I understood that setting correctly, it's for thicker client web apps which are doing fancy stuff like databinding inside the webpage with ActiveX or something: http://www.microsoft.com/technet/prodtechnol/ie/ieak/techinfo/deploy/60/en/secopt.mspx?mfr=true

|||

I got some help from a number of smart people and the following two options look promising:

1. ISA 2006

http://www.microsoft.com/technet/isa/2006/authentication.mspx

2. Protocol Transition

http://justpickanything.adopenstatic.com/cs/blogs/ken/archive/2007/07/18/8460.aspx

Just wanted to give everyone an update.

KeepTogether not working.

Hi all,

I am using RS2005.
KeepTogether=true is not working both in the Preview tab nor when I export to PDF.
My tables still get split by a page break.
RepeatHeaderOnNewPage works as expected.
For a while I was simply putting each table on its own page, but this is such a tacky solution.
Any ideas?

As of now, repeating header on every new page is the only solution.

Shyam

|||

OK.

Thanks Shyam.

|||

So, can you please mark the post as answer?

Shyam

KeepTogether not working.

Hi all,

I am using RS2005.
KeepTogether=true is not working both in the Preview tab nor when I export to PDF.
My tables still get split by a page break.
RepeatHeaderOnNewPage works as expected.
For a while I was simply putting each table on its own page, but this is such a tacky solution.
Any ideas?

As of now, repeating header on every new page is the only solution.

Shyam

|||

OK.

Thanks Shyam.

|||

So, can you please mark the post as answer?

Shyam

KeepTogether not working

I have a main report that contains a table. One detail row of that table
calls to a subreport (which also contains a table). When the entire report
displays, if the main report and subreport data will all fit on one page it
will do so, but if not, the main report goes part of the way down a page
(leaving up to 3/4 of the page blank), then breaks to a new page to display
the subreport data. It seems to try and keep the subreport data table
together more than the main report table. I have KeepTogether set to False on
both tables in the main report and the subreport. The way it is now, the
display format is unacceptable. Please offer any ideas.Stotts, I have exactly the same problem as you. Have you found an answer yet?
"stotts" wrote:
> I have a main report that contains a table. One detail row of that table
> calls to a subreport (which also contains a table). When the entire report
> displays, if the main report and subreport data will all fit on one page it
> will do so, but if not, the main report goes part of the way down a page
> (leaving up to 3/4 of the page blank), then breaks to a new page to display
> the subreport data. It seems to try and keep the subreport data table
> together more than the main report table. I have KeepTogether set to False on
> both tables in the main report and the subreport. The way it is now, the
> display format is unacceptable. Please offer any ideas.|||No, not yet. I applied SP1 hoping it would fix it but no luck. Please let me
know if you find anything.
"Pierre" wrote:
> Stotts, I have exactly the same problem as you. Have you found an answer yet?
> "stotts" wrote:
> > I have a main report that contains a table. One detail row of that table
> > calls to a subreport (which also contains a table). When the entire report
> > displays, if the main report and subreport data will all fit on one page it
> > will do so, but if not, the main report goes part of the way down a page
> > (leaving up to 3/4 of the page blank), then breaks to a new page to display
> > the subreport data. It seems to try and keep the subreport data table
> > together more than the main report table. I have KeepTogether set to False on
> > both tables in the main report and the subreport. The way it is now, the
> > display format is unacceptable. Please offer any ideas.

KeepTogether header does not work correctly.

I selected "Repeat Group Header" in my grouping properties. This is working fine; however, if a group is to start as the last line in a page, the header prints on that last line and then the header is printed once more in the next page. Consequently I end up with two consecutive headers with no detail lines in between.

How do I prevent the printing of two consecutive headers for the same group? I want to get rid of the one that occurs as the last line on the page.

Thanks, Shyam.

The dropdown would not accept a selection of the same group.

I tried other selections, but did not work.

JR.

|||If there is only one such situation in your report, try increasing the height of the detail or the header so that it is stretched to the next page.|||

Thanks for the reply. I appreciated you trying to help me.

I found this problem in several reports and the problem repeats a few times in each report.

I tried your suggestion, it was a good thought, but did not work. It shifted the problem to a different page.

Do you have another suggestion ?

|||

For all the textboxes in the group header, select hide duplicates and select that group in the dropdown below that. It's just a suggestion which may or may not work.

Shyam