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
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
>