Post reply

Getting a syntax error involving Microsoft.SqlServer.SmoEnum

  • November 16, 2006 at 2:09 pm

    #115268

    Last month we upgraded our SQL Server 2000 production database to SQL Server 2005.  It also has SP1 applied to it.  I was just checking the jobs, making certain that everything was running OK.  We have 7 jobs defined, when I clicked on the View Job History link on each of the job's property page, I got a syntax error involving Microsoft.SqlServer.SmoEnum, but really nothing else mentioned.  Here is the text of the error message:

    syntax error (ackup_SystemDBs_Weekly'']) (Microsoft.SqlServer.SmoEnum)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

    Going to the link didn't help me.

    So, how do I find out what's wrong and fix it, please?

     

    Kindest Regards, Rod Connect with me on LinkedIn.

  • November 16, 2006 at 2:11 pm

    #672453

    Sounds like a bug with ssms.  I'd check in with Microsoft.

  • November 16, 2006 at 3:03 pm

    #672473

    What do I do?  Call them up and say something like, "I think I've found a bug in SSMS, can you verify this for me, please?" or something like that?

     

    Kindest Regards, Rod Connect with me on LinkedIn.

  • November 17, 2006 at 6:54 am

    #672578

    how the job was created? and Whats the name of the job?

    Renaming the job should help. can you put profiler and find query which is generating error?

     

  • November 17, 2006 at 6:57 am

    #672583

    I never had to report an error to microsoft.  Search on MS site.. you should find a way to do it.  Other  than calling Bill directly .

  • November 20, 2006 at 9:29 am

    #672998

    Sorry I didn't reply earlier.  We were experiencing network connectivity problems last week Friday.

    Anyway, why is it you believe that renaming the job will help?

     

    Kindest Regards, Rod Connect with me on LinkedIn.

  • November 20, 2006 at 9:32 am

    #673002

    Because of the way the error message was cut.  It seems like the error could have originated because of a forbidden character in the job name.

  • November 20, 2006 at 10:17 am

    #673012

    Oh, I see.  OK.  Because of the original error message, the name of the job should be "Backup_SystemDBs_Weekly".  I have no idea why the job name was missing the beginning "B" in the error message.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • November 20, 2006 at 11:14 am

    #673020

    PS

     

    Did you get this error with ssms when opening the job history or is this the error message you got IN THE HISTORY >> major difference here .

  • November 20, 2006 at 1:19 pm

    #673054

    Ninja's,

    I got the error when I attempted to open (view) the job history.  I've no idea if it is in the history or not.

     

    Kindest Regards, Rod Connect with me on LinkedIn.

  • November 20, 2006 at 1:32 pm

    #673056

    Ok, seems to be a problem with ssms.  Call MS, still don't know how.  Maybe it would be a good time to start a new thread and ask .

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply