I have been asked to maintain an Access 2000 database which is a code front
end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
in an Access database but was later moved to SQL Server 2005 by the Upsizing
tools.)
Some tables have column names which do not conform to the rules given in SQL
Books Online - there are field names with embedded spaces, first character
not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
words. When the tables are viewed via Management Studio, these 'odd' names
are enclosed in square brackets.
The production system is working in this state, but when I try to set up a
test environment on a stand-alone PC, I cannot access these tables. If I try
to link them I get 'ODBC -- Call failed', and if I try to import them I get
error messages about various column names. I can only link to, or import
other tables which do not have these 'odd' field names. If I rename the
columns in SQL server then I can import or link them with no problem.
(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
MDAC 2.8 SP1.)
Somehow the production system works with this data but my test PC doesn't.
What do I need to do on my test PC to use this data with the original 'odd'
column names?
How are you linking the tables? You can write DAO/VBA code to pass the
correctly-delimited table names.
Frankly, you'd be better off just changing the names to conform to
SQLS identifier rules. Having non-compliant names is just going to
cause more headaches down the road. Take the hit now before you've
deployed the app.
-mary
On Fri, 22 Jun 2007 07:54:04 -0700, didub
<didub@.discussions.microsoft.com> wrote:
>I have been asked to maintain an Access 2000 database which is a code front
>end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
>in an Access database but was later moved to SQL Server 2005 by the Upsizing
>tools.)
>Some tables have column names which do not conform to the rules given in SQL
>Books Online - there are field names with embedded spaces, first character
>not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
>words. When the tables are viewed via Management Studio, these 'odd' names
>are enclosed in square brackets.
>The production system is working in this state, but when I try to set up a
>test environment on a stand-alone PC, I cannot access these tables. If I try
>to link them I get 'ODBC -- Call failed', and if I try to import them I get
>error messages about various column names. I can only link to, or import
>other tables which do not have these 'odd' field names. If I rename the
>columns in SQL server then I can import or link them with no problem.
>(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
>MDAC 2.8 SP1.)
>Somehow the production system works with this data but my test PC doesn't.
>What do I need to do on my test PC to use this data with the original 'odd'
>column names?
|||I agree that the column names should be changed to satisfy SQL naming rules,
and I plan to do that, but that is not my first priority.
This app. was created and deployed several years ago by someone who is no
longer with the company. On the live server and desktops it is working with
these invalid names.
My first objective was to install a copy of the system on my own PC so I can
take it apart and plan some major changes and bug fixes. So ideally I would
just like to get my test system working as the live system does.
My guess is that there are some ODBC related settings that I need to change.
Or perhaps there is something I need to do on the SQL Server database. I
have searched Knowledgebase and the forums but I haven't found anything
helpful yet.
"Mary Chipman [MSFT]" wrote:
> How are you linking the tables? You can write DAO/VBA code to pass the
> correctly-delimited table names.
> Frankly, you'd be better off just changing the names to conform to
> SQLS identifier rules. Having non-compliant names is just going to
> cause more headaches down the road. Take the hit now before you've
> deployed the app.
> -mary
> On Fri, 22 Jun 2007 07:54:04 -0700, didub
> <didub@.discussions.microsoft.com> wrote:
>
|||As I recommended earlier, write code so that you can specify the
delimiters. If you're using UI tools then you have no way of knowing
what the unspoken assumptions are - i.e., what is being passed to ODBC
and then the server. Another option is to put a Profiler trace on it
and see what the server is receiving from the client. It's hard to
tell from a distance what's actually going on under the covers with an
app, especially if someone else wrote it.
-mary
On Fri, 22 Jun 2007 15:09:01 -0700, didub
<didub@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I agree that the column names should be changed to satisfy SQL naming rules,
>and I plan to do that, but that is not my first priority.
>This app. was created and deployed several years ago by someone who is no
>longer with the company. On the live server and desktops it is working with
>these invalid names.
>My first objective was to install a copy of the system on my own PC so I can
>take it apart and plan some major changes and bug fixes. So ideally I would
>just like to get my test system working as the live system does.
>My guess is that there are some ODBC related settings that I need to change.
>Or perhaps there is something I need to do on the SQL Server database. I
>have searched Knowledgebase and the forums but I haven't found anything
>helpful yet.
>
>"Mary Chipman [MSFT]" wrote:
Showing posts with label identifier. Show all posts
Showing posts with label identifier. Show all posts
Wednesday, March 21, 2012
Invalid identifier/column names after Upsize Access data to SQL Se
I have been asked to maintain an Access 2000 database which is a code front
end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
in an Access database but was later moved to SQL Server 2005 by the Upsizing
tools.)
Some tables have column names which do not conform to the rules given in SQL
Books Online - there are field names with embedded spaces, first character
not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
words. When the tables are viewed via Management Studio, these 'odd' names
are enclosed in square brackets.
The production system is working in this state, but when I try to set up a
test environment on a stand-alone PC, I cannot access these tables. If I try
to link them I get 'ODBC -- Call failed', and if I try to import them I get
error messages about various column names. I can only link to, or import
other tables which do not have these 'odd' field names. If I rename the
columns in SQL server then I can import or link them with no problem.
(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
MDAC 2.8 SP1.)
Somehow the production system works with this data but my test PC doesn't.
What do I need to do on my test PC to use this data with the original 'odd'
column names?How are you linking the tables? You can write DAO/VBA code to pass the
correctly-delimited table names.
Frankly, you'd be better off just changing the names to conform to
SQLS identifier rules. Having non-compliant names is just going to
cause more headaches down the road. Take the hit now before you've
deployed the app.
-mary
On Fri, 22 Jun 2007 07:54:04 -0700, didub
<didub@.discussions.microsoft.com> wrote:
>I have been asked to maintain an Access 2000 database which is a code front
>end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
>in an Access database but was later moved to SQL Server 2005 by the Upsizin
g
>tools.)
>Some tables have column names which do not conform to the rules given in SQ
L
>Books Online - there are field names with embedded spaces, first character
>not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
>words. When the tables are viewed via Management Studio, these 'odd' names
>are enclosed in square brackets.
>The production system is working in this state, but when I try to set up a
>test environment on a stand-alone PC, I cannot access these tables. If I tr
y
>to link them I get 'ODBC -- Call failed', and if I try to import them I get
>error messages about various column names. I can only link to, or import
>other tables which do not have these 'odd' field names. If I rename the
>columns in SQL server then I can import or link them with no problem.
>(My PC has the latest service packs for SQL Server 2005 and Office 2003, an
d
>MDAC 2.8 SP1.)
>Somehow the production system works with this data but my test PC doesn't.
>What do I need to do on my test PC to use this data with the original 'odd'
>column names?sql
end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
in an Access database but was later moved to SQL Server 2005 by the Upsizing
tools.)
Some tables have column names which do not conform to the rules given in SQL
Books Online - there are field names with embedded spaces, first character
not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
words. When the tables are viewed via Management Studio, these 'odd' names
are enclosed in square brackets.
The production system is working in this state, but when I try to set up a
test environment on a stand-alone PC, I cannot access these tables. If I try
to link them I get 'ODBC -- Call failed', and if I try to import them I get
error messages about various column names. I can only link to, or import
other tables which do not have these 'odd' field names. If I rename the
columns in SQL server then I can import or link them with no problem.
(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
MDAC 2.8 SP1.)
Somehow the production system works with this data but my test PC doesn't.
What do I need to do on my test PC to use this data with the original 'odd'
column names?How are you linking the tables? You can write DAO/VBA code to pass the
correctly-delimited table names.
Frankly, you'd be better off just changing the names to conform to
SQLS identifier rules. Having non-compliant names is just going to
cause more headaches down the road. Take the hit now before you've
deployed the app.
-mary
On Fri, 22 Jun 2007 07:54:04 -0700, didub
<didub@.discussions.microsoft.com> wrote:
>I have been asked to maintain an Access 2000 database which is a code front
>end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
>in an Access database but was later moved to SQL Server 2005 by the Upsizin
g
>tools.)
>Some tables have column names which do not conform to the rules given in SQ
L
>Books Online - there are field names with embedded spaces, first character
>not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
>words. When the tables are viewed via Management Studio, these 'odd' names
>are enclosed in square brackets.
>The production system is working in this state, but when I try to set up a
>test environment on a stand-alone PC, I cannot access these tables. If I tr
y
>to link them I get 'ODBC -- Call failed', and if I try to import them I get
>error messages about various column names. I can only link to, or import
>other tables which do not have these 'odd' field names. If I rename the
>columns in SQL server then I can import or link them with no problem.
>(My PC has the latest service packs for SQL Server 2005 and Office 2003, an
d
>MDAC 2.8 SP1.)
>Somehow the production system works with this data but my test PC doesn't.
>What do I need to do on my test PC to use this data with the original 'odd'
>column names?sql
Wednesday, March 7, 2012
Invalid attribute/option identifier - SQL Server 2000 SP2
From the Enterprise Manager on the server machine, we saw a disconnection to
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.[vbcol=seagreen]
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.[vbcol=seagreen]
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
Invalid attribute/option identifier - SQL Server 2000 SP2
From the Enterprise Manager on the server machine, we saw a disconnection to
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > From the Enterprise Manager on the server machine, we saw a
disconnection
> > to
> > a SQL Server Group. The SQL Server is running and the client worksations
> > are
> > able to run applications against the databases. We got the following
> > error,
> > Invalid attribute/option identifier when trying to register a new
server.
> > Any help would be appricated. Eli
> >
> >
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> > Hi
> >
> > If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> > installation.
> > Ever heard of the virus "slammer"? You are seriously exposed.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > IM: mike@.epprecht.net
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> > "Eli Feng" <efeng@.kerisys.com> wrote in message
> > news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > > From the Enterprise Manager on the server machine, we saw a
> disconnection
> > > to
> > > a SQL Server Group. The SQL Server is running and the client worksations
> > > are
> > > able to run applications against the databases. We got the following
> > > error,
> > > Invalid attribute/option identifier when trying to register a new
> server.
> > > Any help would be appricated. Eli
> > >
> > >
> >
> >
>
>
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > From the Enterprise Manager on the server machine, we saw a
disconnection
> > to
> > a SQL Server Group. The SQL Server is running and the client worksations
> > are
> > able to run applications against the databases. We got the following
> > error,
> > Invalid attribute/option identifier when trying to register a new
server.
> > Any help would be appricated. Eli
> >
> >
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> > Hi
> >
> > If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> > installation.
> > Ever heard of the virus "slammer"? You are seriously exposed.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > IM: mike@.epprecht.net
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> > "Eli Feng" <efeng@.kerisys.com> wrote in message
> > news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > > From the Enterprise Manager on the server machine, we saw a
> disconnection
> > > to
> > > a SQL Server Group. The SQL Server is running and the client worksations
> > > are
> > > able to run applications against the databases. We got the following
> > > error,
> > > Invalid attribute/option identifier when trying to register a new
> server.
> > > Any help would be appricated. Eli
> > >
> > >
> >
> >
>
>
Invalid attribute/option identifier - SQL Server 2000 SP2
From the Enterprise Manager on the server machine, we saw a disconnection to
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. Eli
Hi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>
|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.
>
|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. Eli
Hi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>
|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.
>
|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
Invalid attribute/option identifier
Hello all
I am getting this message when connecting to SQL Server through Enterprise Manager. However all my DSNs work without any problems.
================
A Connection could not be established to DBSERVER.
Reason: Invalid attribute/option identifier.
Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the DBSERVER node) and try again.
================
I have reinstalled SQL Server 2000 and MDAC (ver 2.6) but no success.
Please help!MDAC 2.8 is out - try that.
Also try using NT authentiocation.|||Do not install MDAC by itself. Use SP3 to alter MDAC level.
I am getting this message when connecting to SQL Server through Enterprise Manager. However all my DSNs work without any problems.
================
A Connection could not be established to DBSERVER.
Reason: Invalid attribute/option identifier.
Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the DBSERVER node) and try again.
================
I have reinstalled SQL Server 2000 and MDAC (ver 2.6) but no success.
Please help!MDAC 2.8 is out - try that.
Also try using NT authentiocation.|||Do not install MDAC by itself. Use SP3 to alter MDAC level.
invalid attribute/option identifier
Hi
I currently have a problem with registering a new server in my Enterprise
Manager on a new PC.
I currently have a problem with registering a new server in my Enterprise
Manager on a new PC.
I need to connect to a MSSQL2K server on a windows 2003.
My current PC is on the same LAN as the server and has no problem
registering the server in Enterprise manager. This PC uses NT (about time I
change :-)
The new PC runs WIN2K. But this PC is on another LAN and has to access the
server through a firewall. Port 1433 is open in the firewall.
I use a Firewall-1 authentication agent to access the server.
I use SQL authentification to logon (sa account), I have checked that the
new clients network libraries are the same version as the servers.
In the client network Utility I have set up an alias with the server I want
to access.
The registration seems to access the SQL server, but comes out with an error
stating: "invalid attribute/option identifier"
When I search KB with this message, I get nothing. Did anyone in here
experience anything like this? Any pointers to help me move on would be
greatly appreciated.
best regards
Ren Pedersen"Ren Pedersen" <rpe@.post6.tele.dk> wrote in message
news:4107a915$0$175$edfadb0f@.dtext01.news.tele.dk. ..
> Hi
> I currently have a problem with registering a new server in my Enterprise
> Manager on a new PC.
> I need to connect to a MSSQL2K server on a windows 2003.
> My current PC is on the same LAN as the server and has no problem
> registering the server in Enterprise manager. This PC uses NT (about time
I
> change :-)
> The new PC runs WIN2K. But this PC is on another LAN and has to access the
> server through a firewall. Port 1433 is open in the firewall.
> I use a Firewall-1 authentication agent to access the server.
> I use SQL authentification to logon (sa account), I have checked that the
> new clients network libraries are the same version as the servers.
> In the client network Utility I have set up an alias with the server I
want
> to access.
> The registration seems to access the SQL server, but comes out with an
error
> stating: "invalid attribute/option identifier"
> When I search KB with this message, I get nothing. Did anyone in here
> experience anything like this? Any pointers to help me move on would be
> greatly appreciated.
> best regards
> Ren Pedersen
There are a few hits on Google which suggest reinstalling MDAC and/or the
client tools, plus this post about a specific DLL:
http://groups.google.com/groups?hl=...ng.google .com
Simon|||Worked like a charm - thank you very much.
regards
Ren
"Simon Hayes" <sql@.hayes.ch> skrev i en meddelelse
news:4107ea67$1_2@.news.bluewin.ch...
> "Ren Pedersen" <rpe@.post6.tele.dk> wrote in message
> news:4107a915$0$175$edfadb0f@.dtext01.news.tele.dk. ..
> > Hi
> > I currently have a problem with registering a new server in my
Enterprise
> > Manager on a new PC.
> > I need to connect to a MSSQL2K server on a windows 2003.
> > My current PC is on the same LAN as the server and has no problem
> > registering the server in Enterprise manager. This PC uses NT (about
time
> I
> > change :-)
> > The new PC runs WIN2K. But this PC is on another LAN and has to access
the
> > server through a firewall. Port 1433 is open in the firewall.
> > I use a Firewall-1 authentication agent to access the server.
> > I use SQL authentification to logon (sa account), I have checked that
the
> > new clients network libraries are the same version as the servers.
> > In the client network Utility I have set up an alias with the server I
> want
> > to access.
> > The registration seems to access the SQL server, but comes out with an
> error
> > stating: "invalid attribute/option identifier"
> > When I search KB with this message, I get nothing. Did anyone in here
> > experience anything like this? Any pointers to help me move on would be
> > greatly appreciated.
> > best regards
> > Ren Pedersen
> There are a few hits on Google which suggest reinstalling MDAC and/or the
> client tools, plus this post about a specific DLL:
>
http://groups.google.com/groups?hl=...ng.google .com
> Simon
Invalid attribute/identifier error
HI ,
My application is working fine with SQL Server 2000 ; but when I
change the back end to Oracle 9i it gives an error "Invalid
attribute/identifier" .
Any help would be appreciated .
Thanks ,
Sujay
Hi
SQL Server and Oracle use different dialects of SQL so it is highly unlikely
that the application will work without significant change, even if you have
used ANSI standard SQL the features may not always be fully supported by
either system.
You do not say how far you the application has got, if it is not connecting
then the connection string may be incorrect, if you can track it down to a
specific statement, then run the query in SQL*Plus to see what happens.
John
<ghosh.sujay@.gmail.com> wrote in message
news:1110899405.355947.41090@.f14g2000cwb.googlegro ups.com...
> HI ,
> My application is working fine with SQL Server 2000 ; but when I
> change the back end to Oracle 9i it gives an error "Invalid
> attribute/identifier" .
> Any help would be appreciated .
> Thanks ,
> Sujay
>
My application is working fine with SQL Server 2000 ; but when I
change the back end to Oracle 9i it gives an error "Invalid
attribute/identifier" .
Any help would be appreciated .
Thanks ,
Sujay
Hi
SQL Server and Oracle use different dialects of SQL so it is highly unlikely
that the application will work without significant change, even if you have
used ANSI standard SQL the features may not always be fully supported by
either system.
You do not say how far you the application has got, if it is not connecting
then the connection string may be incorrect, if you can track it down to a
specific statement, then run the query in SQL*Plus to see what happens.
John
<ghosh.sujay@.gmail.com> wrote in message
news:1110899405.355947.41090@.f14g2000cwb.googlegro ups.com...
> HI ,
> My application is working fine with SQL Server 2000 ; but when I
> change the back end to Oracle 9i it gives an error "Invalid
> attribute/identifier" .
> Any help would be appreciated .
> Thanks ,
> Sujay
>
Invalid attribute/identifier error
HI ,
My application runs fine when I am using SQL Server 2000 as its db, but
it gives a message "Invalid attribute/identifier error" when the db is
Oracle .
Any help in this matter would be appreciated .
Thanks ,
Sujay
Sujay Ghosh
Bangalore, INDIA
Email : sujayg_mfc@.yahoo.com
Mobile : 9845467789
Could you provide more detail? Like when the error message happens.
"Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> HI ,
> My application runs fine when I am using SQL Server 2000 as its db,
but
> it gives a message "Invalid attribute/identifier error" when the db is
> Oracle .
> Any help in this matter would be appreciated .
> Thanks ,
> Sujay
> --
> Sujay Ghosh
> Bangalore, INDIA
> Email : sujayg_mfc@.yahoo.com
> Mobile : 9845467789
>
|||Hi ,
Fixed the problem , actually some columns were missing in the referred
procedure .
Thanks ,
Sujay
"Bei Zhu [MSFT]" wrote:
> Could you provide more detail? Like when the error message happens.
> "Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
> news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> but
>
>
My application runs fine when I am using SQL Server 2000 as its db, but
it gives a message "Invalid attribute/identifier error" when the db is
Oracle .
Any help in this matter would be appreciated .
Thanks ,
Sujay
Sujay Ghosh
Bangalore, INDIA
Email : sujayg_mfc@.yahoo.com
Mobile : 9845467789
Could you provide more detail? Like when the error message happens.
"Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> HI ,
> My application runs fine when I am using SQL Server 2000 as its db,
but
> it gives a message "Invalid attribute/identifier error" when the db is
> Oracle .
> Any help in this matter would be appreciated .
> Thanks ,
> Sujay
> --
> Sujay Ghosh
> Bangalore, INDIA
> Email : sujayg_mfc@.yahoo.com
> Mobile : 9845467789
>
|||Hi ,
Fixed the problem , actually some columns were missing in the referred
procedure .
Thanks ,
Sujay
"Bei Zhu [MSFT]" wrote:
> Could you provide more detail? Like when the error message happens.
> "Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
> news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> but
>
>
Invalid attribute/identifier error
HI ,
My application is working fine with SQL Server 2000 ; but when I
change the back end to Oracle 9i it gives an error "Invalid
attribute/identifier" .
Any help would be appreciated .
Thanks ,
SujayHi
SQL Server and Oracle use different dialects of SQL so it is highly unlikely
that the application will work without significant change, even if you have
used ANSI standard SQL the features may not always be fully supported by
either system.
You do not say how far you the application has got, if it is not connecting
then the connection string may be incorrect, if you can track it down to a
specific statement, then run the query in SQL*Plus to see what happens.
John
<ghosh.sujay@.gmail.com> wrote in message
news:1110899405.355947.41090@.f14g2000cwb.googlegroups.com...
> HI ,
> My application is working fine with SQL Server 2000 ; but when I
> change the back end to Oracle 9i it gives an error "Invalid
> attribute/identifier" .
> Any help would be appreciated .
> Thanks ,
> Sujay
>
My application is working fine with SQL Server 2000 ; but when I
change the back end to Oracle 9i it gives an error "Invalid
attribute/identifier" .
Any help would be appreciated .
Thanks ,
SujayHi
SQL Server and Oracle use different dialects of SQL so it is highly unlikely
that the application will work without significant change, even if you have
used ANSI standard SQL the features may not always be fully supported by
either system.
You do not say how far you the application has got, if it is not connecting
then the connection string may be incorrect, if you can track it down to a
specific statement, then run the query in SQL*Plus to see what happens.
John
<ghosh.sujay@.gmail.com> wrote in message
news:1110899405.355947.41090@.f14g2000cwb.googlegroups.com...
> HI ,
> My application is working fine with SQL Server 2000 ; but when I
> change the back end to Oracle 9i it gives an error "Invalid
> attribute/identifier" .
> Any help would be appreciated .
> Thanks ,
> Sujay
>
Invalid attribute/identifier error
HI ,
My application runs fine when I am using SQL Server 2000 as its db, but
it gives a message "Invalid attribute/identifier error" when the db is
Oracle .
Any help in this matter would be appreciated .
Thanks ,
Sujay
Sujay Ghosh
Bangalore, INDIA
Email : sujayg_mfc@.yahoo.com
Mobile : 9845467789Could you provide more detail? Like when the error message happens.
"Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> HI ,
> My application runs fine when I am using SQL Server 2000 as its db,
but
> it gives a message "Invalid attribute/identifier error" when the db is
> Oracle .
> Any help in this matter would be appreciated .
> Thanks ,
> Sujay
> --
> Sujay Ghosh
> Bangalore, INDIA
> Email : sujayg_mfc@.yahoo.com
> Mobile : 9845467789
>|||Hi ,
Fixed the problem , actually some columns were missing in the referred
procedure .
Thanks ,
Sujay
"Bei Zhu [MSFT]" wrote:
> Could you provide more detail? Like when the error message happens.
> "Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
> news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> but
>
>
My application runs fine when I am using SQL Server 2000 as its db, but
it gives a message "Invalid attribute/identifier error" when the db is
Oracle .
Any help in this matter would be appreciated .
Thanks ,
Sujay
Sujay Ghosh
Bangalore, INDIA
Email : sujayg_mfc@.yahoo.com
Mobile : 9845467789Could you provide more detail? Like when the error message happens.
"Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> HI ,
> My application runs fine when I am using SQL Server 2000 as its db,
but
> it gives a message "Invalid attribute/identifier error" when the db is
> Oracle .
> Any help in this matter would be appreciated .
> Thanks ,
> Sujay
> --
> Sujay Ghosh
> Bangalore, INDIA
> Email : sujayg_mfc@.yahoo.com
> Mobile : 9845467789
>|||Hi ,
Fixed the problem , actually some columns were missing in the referred
procedure .
Thanks ,
Sujay
"Bei Zhu [MSFT]" wrote:
> Could you provide more detail? Like when the error message happens.
> "Sujay Ghosh" <sujayg_mfc@.yahoo.com> wrote in message
> news:775763E3-2218-4754-88C6-384CC144AA80@.microsoft.com...
> but
>
>
Subscribe to:
Posts (Atom)