Error connecting to Reporting server

Getting the following error after MS Updates
Reporting Services Error
----
An internal error occurred on the report server. See the error log for more
details. (rsInternalError) Get Online Help
Key not valid for use in specified state.
LOG File entry:
System.Runtime.InteropServices.COMException (0x8009000B): Key not valid for
use in specified state.
Any assistance would be apprectiated.
--
JerryDid you just install the report server?
"Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> Getting the following error after MS Updates
> Reporting Services Error
> ----
> An internal error occurred on the report server. See the error log for
> more
> details. (rsInternalError) Get Online Help
> Key not valid for use in specified state.
> LOG File entry:
> System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> for
> use in specified state.
> Any assistance would be apprectiated.
> --
> Jerry|||No, this had been running successfully for quite awhile, shortly after the
latest MS secuity updates did this happen.
I've checked all of the services and restarted them. I've ran the rsconfig
utility to update the config files, but still the same message.
--
Jerry
"Ben Watts" wrote:
> Did you just install the report server?
> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > Getting the following error after MS Updates
> > Reporting Services Error
> > ----
> >
> > An internal error occurred on the report server. See the error log for
> > more
> > details. (rsInternalError) Get Online Help
> > Key not valid for use in specified state.
> >
> > LOG File entry:
> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > for
> > use in specified state.
> >
> > Any assistance would be apprectiated.
> > --
> > Jerry
>
>|||I found this when I googled your log file entry.
9/20/2005 4:09:21 AM RE: Setup could not initialize the report
server
Hi AJ,
Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
the sufficient information!
From your descriptions, I understood you encoutner the error message "Setup
could not initialize the report server" when initializing the Reporting
Services. If I have misunderstood your concern, please feel free to point
it out.
We could find the following line in the report error logs
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
not valid for use in specified state.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
Based on my knowledge, please perform the steps below and let me know
whether it resolves your issue
1. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
These files represent the Microsoft SQL Server Reporting Services Key
Container.
3. Delete these files.
4. Reinstall Reporting Services.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
"Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> No, this had been running successfully for quite awhile, shortly after the
> latest MS secuity updates did this happen.
> I've checked all of the services and restarted them. I've ran the rsconfig
> utility to update the config files, but still the same message.
> --
> Jerry
>
> "Ben Watts" wrote:
>> Did you just install the report server?
>> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
>> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
>> > Getting the following error after MS Updates
>> > Reporting Services Error
>> > ----
>> >
>> > An internal error occurred on the report server. See the error log for
>> > more
>> > details. (rsInternalError) Get Online Help
>> > Key not valid for use in specified state.
>> >
>> > LOG File entry:
>> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
>> > for
>> > use in specified state.
>> >
>> > Any assistance would be apprectiated.
>> > --
>> > Jerry
>>|||I deleted that file and everything seems to be up and running.
Thank you,
--
Jerry
"Ben Watts" wrote:
> I found this when I googled your log file entry.
> 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> server
> Hi AJ,
> Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> the sufficient information!
> From your descriptions, I understood you encoutner the error message "Setup
> could not initialize the report server" when initializing the Reporting
> Services. If I have misunderstood your concern, please feel free to point
> it out.
> We could find the following line in the report error logs
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> not valid for use in specified state.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> Based on my knowledge, please perform the steps below and let me know
> whether it resolves your issue
> 1. From Explorer, navigate to x:\Documents and Settings\<service
> account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> These files represent the Microsoft SQL Server Reporting Services Key
> Container.
> 3. Delete these files.
> 4. Reinstall Reporting Services.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > No, this had been running successfully for quite awhile, shortly after the
> > latest MS secuity updates did this happen.
> >
> > I've checked all of the services and restarted them. I've ran the rsconfig
> > utility to update the config files, but still the same message.
> >
> > --
> > Jerry
> >
> >
> > "Ben Watts" wrote:
> >
> >> Did you just install the report server?
> >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> >> > Getting the following error after MS Updates
> >> > Reporting Services Error
> >> > ----
> >> >
> >> > An internal error occurred on the report server. See the error log for
> >> > more
> >> > details. (rsInternalError) Get Online Help
> >> > Key not valid for use in specified state.
> >> >
> >> > LOG File entry:
> >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> >> > for
> >> > use in specified state.
> >> >
> >> > Any assistance would be apprectiated.
> >> > --
> >> > Jerry
> >>
> >>
> >>
>
>|||You say 'you deleted the file and everything seems to be running'.
Does that mean that you did NOT reinstall RS?
Jerry Hodson wrote:
> I deleted that file and everything seems to be up and running.
> Thank you,
> --
> Jerry
>
> "Ben Watts" wrote:
> > I found this when I googled your log file entry.
> >
> > 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> > server
> > Hi AJ,
> >
> > Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> >
> > the sufficient information!
> >
> > From your descriptions, I understood you encoutner the error message "Setup
> >
> > could not initialize the report server" when initializing the Reporting
> >
> > Services. If I have misunderstood your concern, please feel free to point
> >
> > it out.
> >
> > We could find the following line in the report error logs
> >
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> >
> > An internal error occurred on the report server. See the error log for more
> >
> > details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> >
> > not valid for use in specified state.
> >
> > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >
> > errorCode, IntPtr errorInfo)
> >
> > Based on my knowledge, please perform the steps below and let me know
> >
> > whether it resolves your issue
> >
> > 1. From Explorer, navigate to x:\Documents and Settings\<service
> >
> > account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> >
> > 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> >
> > These files represent the Microsoft SQL Server Reporting Services Key
> >
> > Container.
> >
> > 3. Delete these files.
> >
> > 4. Reinstall Reporting Services.
> >
> > Thank you for your patience and cooperation. If you have any questions or
> >
> > concerns, don't hesitate to let me know. We are always here to be of
> >
> > assistance!
> >
> > Sincerely yours,
> >
> > Michael Cheng
> >
> > Microsoft Online Partner Support
> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> >
> > that others may learn and benefit from your issue.
> >
> >
> >
> > "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > > No, this had been running successfully for quite awhile, shortly after the
> > > latest MS secuity updates did this happen.
> > >
> > > I've checked all of the services and restarted them. I've ran the rsconfig
> > > utility to update the config files, but still the same message.
> > >
> > > --
> > > Jerry
> > >
> > >
> > > "Ben Watts" wrote:
> > >
> > >> Did you just install the report server?
> > >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > >> > Getting the following error after MS Updates
> > >> > Reporting Services Error
> > >> > ----
> > >> >
> > >> > An internal error occurred on the report server. See the error log for
> > >> > more
> > >> > details. (rsInternalError) Get Online Help
> > >> > Key not valid for use in specified state.
> > >> >
> > >> > LOG File entry:
> > >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > >> > for
> > >> > use in specified state.
> > >> >
> > >> > Any assistance would be apprectiated.
> > >> > --
> > >> > Jerry
> > >>
> > >>
> > >>
> >
> >
> >|||You say 'you deleted the file and everything seems to be running'.
Does that mean that you did NOT reinstall RS?
Jerry Hodson wrote:
> I deleted that file and everything seems to be up and running.
> Thank you,
> --
> Jerry
>
> "Ben Watts" wrote:
> > I found this when I googled your log file entry.
> >
> > 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> > server
> > Hi AJ,
> >
> > Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> >
> > the sufficient information!
> >
> > From your descriptions, I understood you encoutner the error message "Setup
> >
> > could not initialize the report server" when initializing the Reporting
> >
> > Services. If I have misunderstood your concern, please feel free to point
> >
> > it out.
> >
> > We could find the following line in the report error logs
> >
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> >
> > An internal error occurred on the report server. See the error log for more
> >
> > details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> >
> > not valid for use in specified state.
> >
> > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >
> > errorCode, IntPtr errorInfo)
> >
> > Based on my knowledge, please perform the steps below and let me know
> >
> > whether it resolves your issue
> >
> > 1. From Explorer, navigate to x:\Documents and Settings\<service
> >
> > account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> >
> > 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> >
> > These files represent the Microsoft SQL Server Reporting Services Key
> >
> > Container.
> >
> > 3. Delete these files.
> >
> > 4. Reinstall Reporting Services.
> >
> > Thank you for your patience and cooperation. If you have any questions or
> >
> > concerns, don't hesitate to let me know. We are always here to be of
> >
> > assistance!
> >
> > Sincerely yours,
> >
> > Michael Cheng
> >
> > Microsoft Online Partner Support
> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> >
> > that others may learn and benefit from your issue.
> >
> >
> >
> > "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > > No, this had been running successfully for quite awhile, shortly after the
> > > latest MS secuity updates did this happen.
> > >
> > > I've checked all of the services and restarted them. I've ran the rsconfig
> > > utility to update the config files, but still the same message.
> > >
> > > --
> > > Jerry
> > >
> > >
> > > "Ben Watts" wrote:
> > >
> > >> Did you just install the report server?
> > >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > >> > Getting the following error after MS Updates
> > >> > Reporting Services Error
> > >> > ----
> > >> >
> > >> > An internal error occurred on the report server. See the error log for
> > >> > more
> > >> > details. (rsInternalError) Get Online Help
> > >> > Key not valid for use in specified state.
> > >> >
> > >> > LOG File entry:
> > >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > >> > for
> > >> > use in specified state.
> > >> >
> > >> > Any assistance would be apprectiated.
> > >> > --
> > >> > Jerry
> > >>
> > >>
> > >>
> >
> >
> >|||Sorry for taking so long in answering, but that is correct, once I deleted
that file RS started working correctly
--
Jerry
"Steve" wrote:
> You say 'you deleted the file and everything seems to be running'.
> Does that mean that you did NOT reinstall RS?
>
> Jerry Hodson wrote:
> > I deleted that file and everything seems to be up and running.
> >
> > Thank you,
> > --
> > Jerry
> >
> >
> > "Ben Watts" wrote:
> >
> > > I found this when I googled your log file entry.
> > >
> > > 9/20/2005 4:09:21 AM RE: Setup could not initialize the report
> > > server
> > > Hi AJ,
> > >
> > > Welcome to use MSDN Managed Newsgroup and thanks so much for your providing
> > >
> > > the sufficient information!
> > >
> > > From your descriptions, I understood you encoutner the error message "Setup
> > >
> > > could not initialize the report server" when initializing the Reporting
> > >
> > > Services. If I have misunderstood your concern, please feel free to point
> > >
> > > it out.
> > >
> > > We could find the following line in the report error logs
> > >
> > > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > >
> > > An internal error occurred on the report server. See the error log for more
> > >
> > > details. --> System.Runtime.InteropServices.COMException (0x8009000B): Key
> > >
> > > not valid for use in specified state.
> > >
> > > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> > >
> > > errorCode, IntPtr errorInfo)
> > >
> > > Based on my knowledge, please perform the steps below and let me know
> > >
> > > whether it resolves your issue
> > >
> > > 1. From Explorer, navigate to x:\Documents and Settings\<service
> > >
> > > account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
> > >
> > > 2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
> > >
> > > These files represent the Microsoft SQL Server Reporting Services Key
> > >
> > > Container.
> > >
> > > 3. Delete these files.
> > >
> > > 4. Reinstall Reporting Services.
> > >
> > > Thank you for your patience and cooperation. If you have any questions or
> > >
> > > concerns, don't hesitate to let me know. We are always here to be of
> > >
> > > assistance!
> > >
> > > Sincerely yours,
> > >
> > > Michael Cheng
> > >
> > > Microsoft Online Partner Support
> > >
> > > When responding to posts, please "Reply to Group" via your newsreader so
> > >
> > > that others may learn and benefit from your issue.
> > >
> > >
> > >
> > > "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > > news:E944F1D8-2546-4AEB-9665-4E7ED96C6089@.microsoft.com...
> > > > No, this had been running successfully for quite awhile, shortly after the
> > > > latest MS secuity updates did this happen.
> > > >
> > > > I've checked all of the services and restarted them. I've ran the rsconfig
> > > > utility to update the config files, but still the same message.
> > > >
> > > > --
> > > > Jerry
> > > >
> > > >
> > > > "Ben Watts" wrote:
> > > >
> > > >> Did you just install the report server?
> > > >> "Jerry Hodson" <JerryHodson@.discussions.microsoft.com> wrote in message
> > > >> news:EF14EB04-327F-4D6D-9E4C-5121097B3300@.microsoft.com...
> > > >> > Getting the following error after MS Updates
> > > >> > Reporting Services Error
> > > >> > ----
> > > >> >
> > > >> > An internal error occurred on the report server. See the error log for
> > > >> > more
> > > >> > details. (rsInternalError) Get Online Help
> > > >> > Key not valid for use in specified state.
> > > >> >
> > > >> > LOG File entry:
> > > >> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > > >> > for
> > > >> > use in specified state.
> > > >> >
> > > >> > Any assistance would be apprectiated.
> > > >> > --
> > > >> > Jerry
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
>

Error Condition for Updates

Hi,

I have a series of Updates that I perform on 7 tables. I would like to execute these updates on a nighly basis via a job. I have the update statements lined up in a stored proc.

So I have -

Create Proc Update
AS
SET NOCOUNT ON

DECLARE @.RETURNVALUE int
DECLARE @.ERRORMESSAGETXT varchar(510)
DECLARE @.ERRORNUM int

set @.RETURNVALUE = 0

BEGIN --Start here

Update table1
Update table2
.
.
.
Update table7

SELECT @.ERRORNUM = @.@.ERROR
IF @.ERRORNUM = 0
SELECT @.RETURNVALUE = 0
ELSE
BEGIN
SELECT @.ERRORMESSAGETXT = description FROM [master].[dbo].[sysmessages]
WHERE error = @.@.ERROR
RAISERROR (@.ERRORMESSAGETXT, 16, 1)
SELECT @.RETURNVALUE = 1
END
RETURN @.RETURNVALUE
END -- END HERE

--

Is the error checking at the appropriate place? Should I have error conditions after every update? If yes then what condition do I check for?

Thanks@.@.ERROR only shows the result of the most recent statement. It is cleared for the next statement. Therefor your code is only going to indicate whether an error occured on Update Table7.

You will need to check for an error after each critical step, and then store the results of the error check. You can store it in a single value like:
@.ERROR_MONITOR = @.ERROR_MONITOR + @.@.ERROR
...which will result in a value greater than zero if any errors occured. Or you can store the results of each check separately (@.UPDATETABLE1ERROR, @.UPDATETABLE2ERROR..etc).|||So is this correct. Check the where clause in the ELSE part and the statement after Update Table 7.
----
Update table1
SELECT @.ERRORNUM = @.ERRORNUM + @.@.ERROR
Update table2
SELECT @.ERRORNUM = @.ERRORNUM + @.@.ERROR
.
.
.
Update table7
SELECT @.ERRORNUM = @.ERRORNUM + @.@.ERROR

IF @.ERRORNUM = 0
SELECT @.RETURNVALUE = 0
ELSE
BEGIN
SELECT @.ERRORMESSAGETXT = description FROM [master].[dbo].[sysmessages]
WHERE error = @.@.ERROR (OR is this @.ERRORNUM)
RAISERROR (@.ERRORMESSAGETXT, 16, 1)
SELECT @.RETURNVALUE = 1
END
RETURN @.RETURNVALUE

Let me know.

Thanks|||@.ERRORNUM holds the sum of all the error message IDs, so it can be used to determine whether any error occured but if more than one error occured then it is useless for looking up the error description.

"SELECT @.ERRORMESSAGETXT = description FROM [master].[dbo].[sysmessages] WHERE error = @.@.ERROR "
...will, again, only give you the error message for the last error to occur.

If you want to be able to handle multiple errors, create a varchar variable and append any error text to it after each critical step.

Depending on your process, you may just want to exit the procedure after the first error...|||Don't call your procedure "Update". And I don't think you could actually compile what you posted.

And if you are really interested in capturing all the errors while continuing to do your updates, then you'll need a @.temptable to acquire a value of @.@.error on each update. At the end you would parse a string of all errors by joining this table with sysmessages and scrolling through it while concatenating [description] into a varchar variable.