Re: Error: 17883, Severity: 1, State: 0

Sree,

17883 error message is a health detection message that can be triggered for MANY REASONS. Once we get the 17883 message, we need to determine the root cause of
the 17883 message. 17883 message does not necessarily indicate that the issue is a SQL issue. It could be due to various reasons. Yeah, if it was due to a SQL issue and
that issue is fixed in SP4 then you will not see it for that issue after applying SP4.

So, coming to your qs "We ha d a similar issue then we applied 818 patch didn't fix the problem..Assuming this is fixed in SP4" --- What do you mean by a similar issue? Do
you mean that you got the 17883 message? If yes, then that itself does not mean you have similar issue. This is a just a health detection message. To find the root cause,
we will need to review the minidump that gets created after you have 818 patch. So, 818 patch does not fix the 17883 message because 17883 message is not an issue -- it
is just an indicator. 818 did fix many other bugs and gave better error message and created mini dump when 17883 was generated. The mini dump is a starting point for
troubleshooting.

HTH,

Best Regards,

Uttam Parui
Microsoft Corporation

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

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx


.

Relevant Pages

  • Re: Thank God for backups!
    ... Actually if there's nothing in there, your problem may lie elsewhere. ... As before it gives me the error message. ... prevent even root from deleting it. ... Have a look at the permissions, ...
    (Ubuntu)
  • Re: several questions
    ... > reasons be?And how could I restore the users account with least loss? ... Log in as root - ONE ... editor like vi or dtpad that doesn't do any locking, ... > them from editing the password at the same time and let them edit it ...
    (comp.unix.solaris)
  • Re: publishing orchestration as a web service
    ... This is a generic error message. ... Also most common reasons for this error are incorrect/insufficient security ... |>>> ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& ... |>>> unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled, Object ...
    (microsoft.public.biztalk.server)
  • Re: root login with telnetd
    ... without telneting to some user and then su - ... My reasons for this being a bad idea isn't so much from concerns about ... but it's more an issue of accountability. ... the root password on various machines. ...
    (freebsd-questions)
  • Re: pam_acct_mgmt(): user account has expired (was Re: Login
    ... I enter my normal login and then my password. ... > The last error message will repeat with the number getting ... All accounts, including root, are "expired". ... 'pam_acct_mgmt: user accound has expired' ...
    (freebsd-questions)