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

Hi,

Using SSIS, while importing (source i.e. .csv into destination i.e. sql server table), how is it possible to log the source COLUMN which causes the error in the row?

Thanks

Hello Arkiboys,

Many data flow components, including most sources and destinations, support an "Error Ouput" concept whereby you can work with the individual rows of data that could not be successfully processed by a component. This error output includes an ErrorCode and ErrorColumn that you can use in many cases to determine the column that is causing the error.

For more information, I'd suggest taking a look at this:

http://msdn2.microsoft.com/en-us/library/ms141679.aspx

-David

|||

Hi,

I followed the lonk.
Not sure why I do not get the error columns expanded as it says in the link.

Still do not know how to pull the column out i.e. I have a stored procedure which I would like to record the error columns. How do I get these error columns name and rows?

Thanks

Error changing startup parameters after 8patch

Please help! Here is what happened in details:
----
Originally, the SQL Server install placed the data and log files in
d:\Program Files\Microsoft SQL Server\MSSQL\Data\ folder and the error
logs in d:\Program Files\Microsoft SQL Server\MSSQL\Log folder.
----
For syntactical (commands that do not like spaces in folder or file
names) and security and organizational (separate data and logs to
different drives) reasons, I decided to place them in various
locations. Using http://support.microsoft.com/?kbid=224071 as a
guide, I moved the data file to d:\mssql\data\ and log files to
e:\mssql\transaction_log\ and error logs to e:\mssql\error_log\ by
changing the startup parameters:
-dD:\MSSQL\Data\master.mdf
-lE:\MSSQL\Transaction_Log\mastlog.ldf
-eE:\MSSQL\Error_Log
I followed the exact steps detailed from the link ("Moving the Master
Database").
No problems occurred.
----
I remember I ran the above procedures twice because I renamed one of
the Tlog folder to Transaction_Log. Again, that did not pose any
problems.
----
From time to time, Window updates and this patch were installed on
this machine:
- - ---
Title: Cumulative Patch for Microsoft SQL Server (815495)
Date: 23 July 2003
Software:
- Microsoft SQL Server 7.0
- Microsoft Data Engine (MSDE) 1.0
- Microsoft SQL Server 2000
- Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
- Microsoft SQL Server 2000 Desktop Engine (Windows)
Impact: Run code of attacker's choice
Max Risk: Important
Bulletin: MS03-031
Microsoft encourages customers to review the Security Bulletins at:
http://www.microsoft.com/technet/security/bulletin/MS03-031.asp
http://www.microsoft.com/security/security_bulletins/ms03-031.asp
- ---
----
The next time, I again attempted to change the location of the error
log file by changing the startup parameters to
-eD:\MSSQL\Process_Log\SQL_Error_Log. On step 8 of the "Moving the
Master Database" instructions, SQL Server was having problems starting
up. The error message received was:
initerrlog: Could not open error log file
'D:\MSSQL\Process_Log\SQL_Error_Log'. Operating system error = 5(Access is denied.).
You could not start SQL Server from anywhere except I found that
running sqlservr.exe from the command prompt with the temporary
startup parameters of the error log file of the original location
worked (sqlservr.exe -eD:\Program Files\Microsoft SQL
Server\MSSQL\Log). SQL server runs under this mode, but SQL Server
Agent cannot start up even still.
While the SQL Server is running using the above command, I attempted
to change the Master Start Parameters of the Error Log back to
-eE:\MSSQL\Error_Log
and even -ed:\Program Files\Microsoft SQL Server\MSSQL\Log
but found no success starting the SQL Server with Enterprise Manager
or Services interfaces (sqlservr.exe was shutdown prior to attempt).
----
I am led to believe that the patch 815495 may have been involved with
the error. There have been times where Enterprise Manager freezes up
and automatically shuts down (occurs at least once a week) when
working within EM such as opening properties of Database Maintenance
Plan. This had not occurred before. In addition all the SQL logs
have been wiped out.
I have installed the same patch to my personal WinXP machine and the
Enterprise Manager no longer works (unable to open and receive an
error message to forward error to Microsoft) even with a reinstall.
These same results occurred on two server machines which were prepared
for production and standby. I don't know what else to do? Please
help!
Thanks so much,
JuneThe Error message you are receiving is access is denied to the log files.
Check your NTFS permissions, and make sure that the SQL Server account has
full control of the log files and the folder that they are in.
--
Denny Cherry
DBA
GameSpy Industries
"June" <jnguyen@.harbourcg.com> wrote in message
news:29f6d8aa.0309121232.54032ff@.posting.google.com...
> Please help! Here is what happened in details:
> ----
--
> Originally, the SQL Server install placed the data and log files in
> d:\Program Files\Microsoft SQL Server\MSSQL\Data\ folder and the error
> logs in d:\Program Files\Microsoft SQL Server\MSSQL\Log folder.
> ----
--
> For syntactical (commands that do not like spaces in folder or file
> names) and security and organizational (separate data and logs to
> different drives) reasons, I decided to place them in various
> locations. Using http://support.microsoft.com/?kbid=224071 as a
> guide, I moved the data file to d:\mssql\data\ and log files to
> e:\mssql\transaction_log\ and error logs to e:\mssql\error_log\ by
> changing the startup parameters:
> -dD:\MSSQL\Data\master.mdf
> -lE:\MSSQL\Transaction_Log\mastlog.ldf
> -eE:\MSSQL\Error_Log
> I followed the exact steps detailed from the link ("Moving the Master
> Database").
> No problems occurred.
> ----
--
> I remember I ran the above procedures twice because I renamed one of
> the Tlog folder to Transaction_Log. Again, that did not pose any
> problems.
> ----
--
> From time to time, Window updates and this patch were installed on
> this machine:
> - - ---
> Title: Cumulative Patch for Microsoft SQL Server (815495)
> Date: 23 July 2003
> Software:
> - Microsoft SQL Server 7.0
> - Microsoft Data Engine (MSDE) 1.0
> - Microsoft SQL Server 2000
> - Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
> - Microsoft SQL Server 2000 Desktop Engine (Windows)
> Impact: Run code of attacker's choice
> Max Risk: Important
> Bulletin: MS03-031
> Microsoft encourages customers to review the Security Bulletins at:
> http://www.microsoft.com/technet/security/bulletin/MS03-031.asp
> http://www.microsoft.com/security/security_bulletins/ms03-031.asp
> - ---
> ----
--
> The next time, I again attempted to change the location of the error
> log file by changing the startup parameters to
> -eD:\MSSQL\Process_Log\SQL_Error_Log. On step 8 of the "Moving the
> Master Database" instructions, SQL Server was having problems starting
> up. The error message received was:
> initerrlog: Could not open error log file
> 'D:\MSSQL\Process_Log\SQL_Error_Log'. Operating system error => 5(Access is denied.).
> You could not start SQL Server from anywhere except I found that
> running sqlservr.exe from the command prompt with the temporary
> startup parameters of the error log file of the original location
> worked (sqlservr.exe -eD:\Program Files\Microsoft SQL
> Server\MSSQL\Log). SQL server runs under this mode, but SQL Server
> Agent cannot start up even still.
> While the SQL Server is running using the above command, I attempted
> to change the Master Start Parameters of the Error Log back to
> -eE:\MSSQL\Error_Log
> and even -ed:\Program Files\Microsoft SQL Server\MSSQL\Log
> but found no success starting the SQL Server with Enterprise Manager
> or Services interfaces (sqlservr.exe was shutdown prior to attempt).
> ----
--
> I am led to believe that the patch 815495 may have been involved with
> the error. There have been times where Enterprise Manager freezes up
> and automatically shuts down (occurs at least once a week) when
> working within EM such as opening properties of Database Maintenance
> Plan. This had not occurred before. In addition all the SQL logs
> have been wiped out.
> I have installed the same patch to my personal WinXP machine and the
> Enterprise Manager no longer works (unable to open and receive an
> error message to forward error to Microsoft) even with a reinstall.
> These same results occurred on two server machines which were prepared
> for production and standby. I don't know what else to do? Please
> help!
> Thanks so much,
> June

Error attempting to unlock unowned resource

I get the following error when running a procedure tree
Process ID 55 attempting to unlock unowned resource PAG:8:1:4889
And in the server log : Error: 1203, Severity: 20, State: 1
This error is referenced more than one before SP3, but newer since.
I saw all KB to see if some query type are similar to mine, without success.
The following query is executed inside a procedure at the 4th level,
without transaction.
I couln't simply reproduce the problem without calling the first, who's
calling the second, ...
Standalone calling the procedure works like a charm.
Thanks in advance for your help.
Involving query :
DECLARE @.i_tou_niveau INT
SELECT @.i_tou_niveau = 6
UPDATE liasse_rq SET
lia_trav1 = @.i_tou_niveau,
lia_trav3 = o.p_ocd_regr
FROM liasse_rq l, ocd_regr o
WHERE l.lia_c_type_vdd = "PTT"
AND l.lia_niveau BETWEEN 1 AND 2
AND l.p_tou_id = 0
AND o.ocd_niveau = @.i_tou_niveau
AND o.ocd_min <= l.lia_ocd
AND o.ocd_max >= l.lia_ocd
Tables:
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[ocd_regr]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[ocd_regr]
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[liasse_rq]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[liasse_rq]
GO
if exists (select * from dbo.systypes where name =
N't_code')
exec sp_droptype N't_code'
GO
if exists (select * from dbo.systypes where name =
N't_npa')
exec sp_droptype N't_npa'
GO
setuser
GO
EXEC sp_addtype N't_code', N'varchar (4)', N'null'
GO
setuser
GO
setuser
GO
EXEC sp_addtype N't_npa', N'varchar (10)', N'null'
GO
setuser
GO
CREATE TABLE [dbo].[ocd_regr] (
[p_ocd_regr] [varchar] (7) COLLATE French_CI_AI
NOT NULL ,
[ocd_nom] [varchar] (20) COLLATE French_CI_AI NOT
NULL ,
[ocd_min] [int] NOT NULL ,
[ocd_max] [int] NOT NULL ,
[ocd_niveau] [tinyint] NOT NULL ,
[timestamp] [timestamp] NULL
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[liasse_rq] (
[p_lia_id] [int] IDENTITY (1, 1) NOT NULL ,
[lia_c_type_vdd] [t_code] NOT NULL ,
[p_tou_id] [int] NOT NULL ,
[p_vdd_id] [int] NOT NULL ,
[p_edi_id] [int] NOT NULL ,
[lia_nom] [varchar] (28) COLLATE French_CI_AI NOT
NULL ,
[lia_mode_encartage] [tinyint] NOT NULL ,
[lia_qte] [int] NOT NULL ,
[lia_pos] [int] NOT NULL ,
[lia_niveau] [tinyint] NOT NULL ,
[p_pay_id] [int] NULL ,
[lia_npa] [t_npa] NULL ,
[lia_b_ptt2plis] [tinyint] NOT NULL ,
[lia_b_mono] [tinyint] NOT NULL ,
[lia_ocd] [int] NULL ,
[lia_circonscription] [int] NULL ,
[p_amb_id] [int] NULL ,
[p_etr_id] [int] NULL ,
[lia_c_achemin_pe] [t_code] NULL ,
[lia_npa_n] [int] NULL ,
[p_ocd_regr] [varchar] (7) COLLATE French_CI_AI
NULL ,
[lia_trav1] [int] NULL ,
[lia_trav2] [int] NULL ,
[lia_trav3] [varchar] (10) COLLATE French_CI_AI
NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[ocd_regr] WITH NOCHECK ADD
CONSTRAINT [ocd_regr_pk] PRIMARY KEY CLUSTERED
(
[p_ocd_regr]
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[liasse_rq] WITH NOCHECK ADD
CONSTRAINT [liasse_rq_pk] PRIMARY KEY CLUSTERED
(
[p_lia_id]
) ON [PRIMARY]
GO
CREATE UNIQUE INDEX [ocd_regr_u1] ON [dbo].[ocd_regr]
([ocd_niveau], [ocd_min], [ocd_max], [p_ocd_regr]) ON
[PRIMARY]
GO
CREATE INDEX [liasse_rq_i1] ON [dbo].[liasse_rq]
([p_tou_id]) ON [PRIMARY]
GO
Server Info:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: )
Did you able to fix this problem? Plese let me know...