Unable to read local eventlog (the parameter is incorrect)

Unable to read local eventlog (the parameter is incorrect)

• Kutlu

  Where can I get the SP1 Beta

  Michael

  
  
  

• C57682

  hi i have the same problems:
  Ereignistyp: Fehler
  Ereignisquelle: SQLAgent$I1
  Ereigniskategorie: Alert Engine
  Ereigniskennung: 318
  Datum: 21.03.2006
  Zeit: 00:59:42
  Benutzer: Nicht zutreffend
  Computer: HG-ALVB304
  Beschreibung:
  Unable to read local eventlog (reason: Falscher Parameter).

  yesterday i installed SP1 CTP and was hopefull that the problem is solved, but it continues to happen.

  see the version of sql-server:
  Microsoft SQL Server 2005 - 9.00.2040.00 (Intel X86)
  Mar 13 2006 11:20:51
  Copyright (c) 1988-2005 Microsoft Corporation
  Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

  Has anyone an idea

  Weitere Informationen uber die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
  

  
  

• Chris Nieboer

  From our internal testing alerts get triggered , this is the noisy message that gets logged in SQLAgent global event log.

  Gops Dwarak,

  Program Manager, Microsoft

  
  
  

• Rick Hodder

  I've also got this problem - can you please post where the Service Pack is...
  

• nemesisv

  Please complete the following nomination form and send it across(gdwarak@microsoft.com) and I can nominate you to
  participate in Microsoft SQL Server 2005 Service Pack 1 Beta.

  
  Selected testers will receive a welcome email with login instructions once the beta begins.

  * indicates required fields.

  
  Contact Information
  
  Passport Network Account Email Address (This email address must be the one used by the tester to create their Passport)
  *
  First Name (20 characters maximum)
  *
  Middle Name (20 characters maximum)
  
  Last Name (20 characters maximum)
  *
  Company (30 characters maximum)
  
  Address 1 (Use only physical street addresses - No PO Boxes)(30 characters maximum)
  *
  Address 2 (30 characters maximum)
  
  Country
  *
  City
  *
  State/Province
  
  Postal Code (If not applicable enter N/A)
  *
  
  Phone Number
  (Please include your International Country code, and area/city code. Example: 011-555-555-5555
  *
  Phone Extension
  
  Primary Email
  *
  Alternate Email
  
  Have you used/tested SQL Server 2005
  Yes
  No
  *
  If yes, please provide a brief description.
  
  Will you test SQL Server 2005 Express SP1 Beta
  Yes
  No
  *
  Please select all the technologies you will be testing.
  Analysis Services
  Integration Services
  Management Tools
  Notification Services
  Replication
  Reporting Services
  Setup
  SQL Native Client
  SQL Engine
  *
  Do you have a current Standard NDA Agreement
  1. Yes
  2. No
  3. A Standard NDA is being created for the customer
  *
  Note: Once I submit your nomination, selected testers will receive a welcome email once the beta begins.
  When they receive the welcome email they will be able to login to Beta Place, log bugs, download
  the build and obtain newsgroup info.
  

  Thanks,

  Gops Dwarak

  
  
  

• and65

  We have a tracking bug for this and is planned to get fixed in the next public release.
  
  Thanks,
  Gops Dwarak
  
  This posting is provided "AS IS" with no warranties, and
  confers no rights
  

  
  
  

• Joku

  A beta service pack Not particularly interested, how about a hotfix or workaround At this point I’m seeing this error on 5 different servers (all Windows 2003 x86, SP1) does not seem to occur on Windows 2003 x64 servers.

  
  

• Bibble

  Yes, this also occurs on Windows 2003 64 bit. We are running clustered with same error.

  When will the SP1 go from Beta to RTM

  
  

• Arik Cohen - msft

  I am getting the same error on SQL Server 2005 Enterprise after upgrading from 2000 SP3. The service runs as LocalSystem on a domain controller.
  

• Clemens de Brouwer

  What is the status of this bug I just recently had two seperate servers go absolutely bonkers, flooding the SQL Server error logs and application logs with these errors... one machine has since settled down after a restart of the SQL Server agent, the other continues to throw this error every hour or so...

  Thanks,

  Joe

  
  

• dougn

  I'm also getting this same error and unable to find SP1 beta. I'd also like to know how to download it. Thanks.

  Elaine

  
  

• maddinthegreat

  I just discovered this also.

  Can someone clarify please: Does this mean that alerts just flat don't work in 2k5

  -g

  
  
  

• -M-

  I have the same problem for months on a production server. Is there any patch to this obvious product defect There is no SQL Server 2005 SP1 Beta on MSDN Subscriber downloads, at least in English. Or maybe they are posting the Japanese version first and I was not checking in the proper place
  

• meFox

  This is fixed in SP1 Beta and is available for download.

  Thanks,

  Gops Dwarak

  
  
  
• Unable to read local eventlog (the parameter is incorrect)