Wednesday, March 7, 2012

invalid attribute/option identifier

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"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

No comments:

Post a Comment