Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 08/15/04
- Next message: Sue Hoegemeier: "Re: BUG"
- Previous message: Sue Hoegemeier: "Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP"
- In reply to: Andy Svendsen: "Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP"
- Next in thread: Sue Hoegemeier: "Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 15 Aug 2004 12:39:20 -0600
You can get ODBC errors using Query Analyzer - Query
Analyzer connects to SQL Server using ODBC. Plenty of apps
can connect via ODBC and without any ODBC data sources set
up (i.e. DSN-less connections).
-Sue
On Fri, 13 Aug 2004 15:06:46 -0400, "Andy Svendsen"
<andymcdba1@NOMORESPAM.yahoo.com> wrote:
>Don't let the ODBC errors get you thrown off. They are used for ODBC Data
>Sources, not Query Analyzer. When you are able to connect with SQL Query
>Analyzer, an entry gets written to SQL Client Network Utility (cliconfg.exe)
>under Aliases. Have you tried running client network utility and SQL server
>network utility on the server to make sure both programs are communicating
>on the same protocol.
- Next message: Sue Hoegemeier: "Re: BUG"
- Previous message: Sue Hoegemeier: "Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP"
- In reply to: Andy Svendsen: "Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP"
- Next in thread: Sue Hoegemeier: "Re: SQLServerAgent will not start - "Event ID: 103" - URGENT HELP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|