Re: Decode an error message
From: Eric (EricHigg_at_gmail.com)
Date: 01/18/05
- Previous message: Bubi Khan: "Re: Proxy management point - SMS 2003"
- Next in thread: Eric: "Re: Decode an error message"
- Maybe reply: Eric: "Re: Decode an error message"
- Messages sorted by: [ date ] [ thread ]
Date: 18 Jan 2005 13:32:52 -0800
I am getting a similar error from the collection evaluator: Microsoft
SQL Server reported SQL message 207, severity 16:
[42S22][207][Microsoft][ODBC SQL Server Driver][SQL Server]Invalid
column name 'ChassisTypes00'.
I've ruled out legacy clients, and mof issues. Not all collections are
having errors, in fact the majority are ok. There doesn't seem to be a
reason I can see that makes any collection stand out from another.
Any help is much appreciated.
Thanks,
-Eric
Stan White [MS] wrote:
> What SMS component is generating this error?
> Do you ahve the entire SQL statement from the component log? - is it
trying
> to insert a discovery record, run a query, etc?
>
> --
> --
> Stan [MSFT]
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> --
> --
>
> "Jaye" <jaye.roberts@specializedloanservicing.com> wrote in message
> news:u7Di0uGLEHA.1484@tk2msftngp13.phx.gbl...
> > Hello, I am getting a lot of these errors on my SMS server. It
has to do
> > with its connection to our SQL server but I have verified that it
can
> > connect and that there are enough user connections available. Has
anyone
> > seen this before or know what else I can try to fix it? Here is
the error
> > message...
> >
> > Microsoft SQL Server reported SQL message 207, severity 16:
> > [42S22][207][Microsoft][ODBC SQL Server Driver][SQL Server]Invalid
column
> > name 'Last_Logon_User_Name0'.
> >
> > Thank you,
> >
> > ~Jaye
> >
> >
- Previous message: Bubi Khan: "Re: Proxy management point - SMS 2003"
- Next in thread: Eric: "Re: Decode an error message"
- Maybe reply: Eric: "Re: Decode an error message"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|