Error: 17883, Severity: 1, State: 0

MS SQL Server 2000 sp4 Got a series of errors:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 8 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 104:0 (fd4) UMS Context 0x0775B548 appears to be non-yielding on
Scheduler 0.
SQL Server has encountered 37 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [e:\Microsoft SQL
Server\\webslog631_2.mdf] in database [webslog631_2] (35). The OS file handle
is 0x0000071C. The offset of the latest long IO is: 0x0000007e6b8000
Looks like there is a post sp4 hotfix to fix this..
http://support.microsoft.com/kb/909734
how do I contacty MS without having to give them a Credit Card number?"itsonlyme4" wrote:
> MS SQL Server 2000 sp4 Got a series of errors:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 8 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 104:0 (fd4) UMS Context 0x0775B548 appears to be non-yielding on
> Scheduler 0.
> SQL Server has encountered 37 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [e:\Microsoft SQL
> Server\\webslog631_2.mdf] in database [webslog631_2] (35). The OS file handle
> is 0x0000071C. The offset of the latest long IO is: 0x0000007e6b8000
> Looks like there is a post sp4 hotfix to fix this..
> http://support.microsoft.com/kb/909734
> how do I contacty MS without having to give them a Credit Card number?
>
Hi
The cumulative update pack is publically available and will contain this fix
http://support.microsoft.com/kb/916287/
John

error with assebly

On preview custom assebly returns correct value - works OK, but on server i get an error like "#Error". Is it possible to debug report on server?
Thanks.Your custom assembly may not have permissions to do what you want it to do.
You'll need to edit the rssrvpolicy.config file and give it appropriate
permissions. Check
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_rdl_8mue.asp.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
<AG>; "NLB d.d." <AGNLBdd@.discussions.microsoft.com> wrote in message
news:4AE2405E-5DB7-4B48-82B8-4F8846112038@.microsoft.com...
> On preview custom assebly returns correct value - works OK, but on server
i get an error like "#Error". Is it possible to debug report on server?
> Thanks.
>

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.