Error doing "Process Update" on some dimensions

When processing some of the dimensions in my database using "Process Update" I get an internal error from the OLAP Engine (no specification)... Any known bugs on this, or am I just missing something?

This one is really bugging me Has anyone else had similar experiences?

|||Hy , i have this error too in Sql/olap 2005.|||Having gotten some new information from Microsoft, I am quite certain that this is a bug. Microsoft should be aware of it, and a fix will hopefully make it into SP1.|||

Can you post here bit more information about your situation:

The error description.
What stage it is happening: Beginning, end.
Information about your dimension structure.
Sizes.

Can you try and monitor Analysis Server using SQL Profiler while processing is going, see what is happening before the error occurs

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Error doing "Process Update" on some dimensions

When processing some of the dimensions in my database using "Process Update" I get an internal error from the OLAP Engine (no specification)... Any known bugs on this, or am I just missing something?

This one is really bugging me Has anyone else had similar experiences?

|||Hy , i have this error too in Sql/olap 2005.|||Having gotten some new information from Microsoft, I am quite certain that this is a bug. Microsoft should be aware of it, and a fix will hopefully make it into SP1.|||

Can you post here bit more information about your situation:

The error description.
What stage it is happening: Beginning, end.
Information about your dimension structure.
Sizes.

Can you try and monitor Analysis Server using SQL Profiler while processing is going, see what is happening before the error occurs

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

sql

Error deleting a folder

When we try to delete a folder in de report manager we get an internal error
from the Report server .
In the log we find:
w3wp!library!8!04/25/2007-12:46:33:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., un-named assertion fired for component library;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details.
w3wp!library!11!04/25/2007-12:46:45:: i INFO: Call to GetSystemPermissions
w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to GetSystemPermissions
w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to CreateFolder( 'New
Folder', '/')
w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to GetPermissions:/
w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to GetSystemPermissions
w3wp!library!8!04/25/2007-12:47:04:: i INFO: Exception dumped to: C:\Program
Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles flags= ReferencedMemory, AllThreads, SendToWatson
w3wp!library!8!04/25/2007-12:47:09:: i INFO: Call to RenderFirst(
'/Boordtabel/dummy' )
w3wp!webserver!8!04/25/2007-12:47:10:: i INFO: Processed report.
Report='/Boordtabel/dummy', Stream=''
w3wp!library!1!04/25/2007-12:47:12:: i INFO: Call to GetPermissions:/
w3wp!library!11!04/25/2007-12:47:12:: i INFO: Call to GetSystemPermissions
w3wp!library!1!04/25/2007-12:47:12:: i INFO: Call to DeleteItem( '/New
Folder' )
w3wp!library!1!04/25/2007-12:47:12:: a ASSERT: Assertion failed! Call stack:
Microsoft.ReportingServices.Library.RSService._DeleteItem(String item)
Microsoft.ReportingServices.Library.RSService.ExecuteBatch(Guid batchId)
Microsoft.ReportingServices.WebServer.ReportingService2005.ExecuteBatch()
System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target,
Object[] values)
System.Web.Services.Protocols.WebServiceHandler.Invoke()
System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
System.Web.HttpApplication.ResumeSteps(Exception error)
System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)
w3wp!library!1!04/25/2007-12:47:12:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., un-named assertion fired for component library;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details.
Any ideas?On Apr 25, 6:06 am, Antoon <Ant...@.discussions.microsoft.com> wrote:
> When we try to delete a folder in de report manager we get an internal error
> from the Report server .
> In the log we find:
> w3wp!library!8!04/25/2007-12:46:33:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details., un-named assertion fired for component library;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details.
> w3wp!library!11!04/25/2007-12:46:45:: i INFO: Call to GetSystemPermissions
> w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to GetSystemPermissions
> w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to CreateFolder( 'New
> Folder', '/')
> w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to GetPermissions:/
> w3wp!library!11!04/25/2007-12:46:48:: i INFO: Call to GetSystemPermissions
> w3wp!library!8!04/25/2007-12:47:04:: i INFO: Exception dumped to: C:\Program
> Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles flags=> ReferencedMemory, AllThreads, SendToWatson
> w3wp!library!8!04/25/2007-12:47:09:: i INFO: Call to RenderFirst(
> '/Boordtabel/dummy' )
> w3wp!webserver!8!04/25/2007-12:47:10:: i INFO: Processed report.
> Report='/Boordtabel/dummy', Stream=''
> w3wp!library!1!04/25/2007-12:47:12:: i INFO: Call to GetPermissions:/
> w3wp!library!11!04/25/2007-12:47:12:: i INFO: Call to GetSystemPermissions
> w3wp!library!1!04/25/2007-12:47:12:: i INFO: Call to DeleteItem( '/New
> Folder' )
> w3wp!library!1!04/25/2007-12:47:12:: a ASSERT: Assertion failed! Call stack:
> Microsoft.ReportingServices.Library.RSService._DeleteItem(String item)
> Microsoft.ReportingServices.Library.RSService.ExecuteBatch(Guid batchId)
> Microsoft.ReportingServices.WebServer.ReportingService2005.ExecuteBatch()
> System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
> arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
> RuntimeTypeHandle typeOwner)
> System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
> arguments, Signature sig, MethodAttributes methodAttributes,
> RuntimeTypeHandle typeOwner)
> System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
> skipVisibilityChecks)
> System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target,
> Object[] values)
> System.Web.Services.Protocols.WebServiceHandler.Invoke()
> System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
> System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
> System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously)
> System.Web.HttpApplication.ResumeSteps(Exception error)
> System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
> System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
> System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)
> w3wp!library!1!04/25/2007-12:47:12:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details., un-named assertion fired for component library;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details.
> Any ideas?
This posting might be of assistance.
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/ebfe917dd50ecb0c/b6c5fe0bc216e8c7?lnk=st&q=Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException%3A+&rnum=5#b6c5fe0bc216e8c7
Regards,
Enrique Martinez
Sr. Software Consultant

Error connecting to sql server

I have a perplexing problem. I've developed an ASP application for our internal business use. I'm getting ready to launch, but every once in a while the application can't connect to the database. The error I get is:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

We (IT and I) turned off the remote connections and it still happens. I'm afraid of launching without understanding what causes this and gettign a fix. To get it working again, we restart IIS and it works fine. I used VWD 2005 Express and it's running on SQL Server 2005 Express.

Thanks for any help you may have.
Scott J.

Don't let the bit about "does not allow remote connections" send you down the wrong path - this ridiculous error message is posted regardless of the actual problem (one of Microsoft's worst error messages).

The part to concentrate on is the final part of the error message, which differs depending on the actual error - in your case error: 40 - Could not open a connection to SQL Server. Are you sure that the SQL Express instance is actually running when you get this problem (is it periodically stopping?). Check it via the services applet - restarting IIS may simply be restarting the Express instance.

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