Database Server not found after upgrade from ASA 9 to SQLAnywhere 11

Our database server was running under ASA 9 and we were connecting from 
client computers using the following odbc profile...

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_works]
"Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 9\\win32\\dbodbc9.dll"
"UID"="dba"
"PWD"="*********"
"DatabaseName"="albatross"
"EngineName"="\\\\07-06-tides\\albatross_00"
"AutoStop"="Yes"
"Integrated"="No"
"Debug"="No"
"DisableMultiRowFetch"="No"
"CommLinks"="SharedMemory,TCPIP{},SPX{},NamedPipes"
"Compress"="No"
"Description"="DB"

I recently updated the database server to SQL Anywhere 11.  I can connect to 
the database on the server itself, but if a client trys to connect using the 
following SQL Anywhere 11 odbc profile, I get a "Database server not found" 
error.

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
"Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
"UserID"="dba"
"Password"="********"
"ServerName"="\\\\07-06-tides\\albatross_00"
"AutoStop"="YES"
"Integrated"="NO"
"Debug"="NO"
"DisableMultiRowFetch"="NO"
"CommLinks"="SharedMemory,TCPIP{}"
"Compress"="NO"
"Description"="DB"
"DatabaseName"="albatross"

I can connect to the server just fine if I use the ASA 9 odbc profile.  But 
for some reason the SQL Anywhere 11 profile won't work.  What am I missing? 
I'm using version 11.0.1.2044.

Thanks.

Shenn Sellers


0
Shenn
9/15/2009 4:35:59 PM
sybase.sqlanywhere.general 32637 articles. 22 followers. Follow

6 Replies
1229 Views

Similar Articles

[PageSpeed] 50
Get it on Google Play
Get it on Apple App Store

While we sometimes see server names like that
this usage

     "EngineName"="\\\\07-06-tides\\albatross_00"

sometimes indicate a flawed configuraton there. When
you start the server, what -n switches do you use?
[in fact show you entire start line or service parameters]

By specifying DEBUG=Yes and LOG=filename.txt
for both you can maybe capture the context of the
way the succeeding connection works and be able to
compare those. [actually debug= is historical and
ignored in both versions I believe, you just need
LOG=filename.txt for it to work]

Also watch our for any asasrv.ini and sasrv.ini
files since they do interact here.



"Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message 
news:4aafc26f$1@forums-1-dub...
> Our database server was running under ASA 9 and we were connecting from 
> client computers using the following odbc profile...
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_works]
> "Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 9\\win32\\dbodbc9.dll"
> "UID"="dba"
> "PWD"="*********"
> "DatabaseName"="albatross"
> "EngineName"="\\\\07-06-tides\\albatross_00"
> "AutoStop"="Yes"
> "Integrated"="No"
> "Debug"="No"
> "DisableMultiRowFetch"="No"
> "CommLinks"="SharedMemory,TCPIP{},SPX{},NamedPipes"
> "Compress"="No"
> "Description"="DB"
>
> I recently updated the database server to SQL Anywhere 11.  I can connect 
> to the database on the server itself, but if a client trys to connect 
> using the following SQL Anywhere 11 odbc profile, I get a "Database server 
> not found" error.
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
> "UserID"="dba"
> "Password"="********"
> "ServerName"="\\\\07-06-tides\\albatross_00"
> "AutoStop"="YES"
> "Integrated"="NO"
> "Debug"="NO"
> "DisableMultiRowFetch"="NO"
> "CommLinks"="SharedMemory,TCPIP{}"
> "Compress"="NO"
> "Description"="DB"
> "DatabaseName"="albatross"
>
> I can connect to the server just fine if I use the ASA 9 odbc profile. 
> But for some reason the SQL Anywhere 11 profile won't work.  What am I 
> missing? I'm using version 11.0.1.2044.
>
> Thanks.
>
> Shenn Sellers
>
> 


0
Nick
9/15/2009 5:16:29 PM
Also adding
      "a -z -o filename.txt"
to the servers will capture the context
on that side as well.

"Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in 
message news:4aafcbed$1@forums-1-dub...
> While we sometimes see server names like that
> this usage
>
>     "EngineName"="\\\\07-06-tides\\albatross_00"
>
> sometimes indicate a flawed configuraton there. When
> you start the server, what -n switches do you use?
> [in fact show you entire start line or service parameters]
>
> By specifying DEBUG=Yes and LOG=filename.txt
> for both you can maybe capture the context of the
> way the succeeding connection works and be able to
> compare those. [actually debug= is historical and
> ignored in both versions I believe, you just need
> LOG=filename.txt for it to work]
>
> Also watch our for any asasrv.ini and sasrv.ini
> files since they do interact here.
>
>
>
> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message 
> news:4aafc26f$1@forums-1-dub...
>> Our database server was running under ASA 9 and we were connecting from 
>> client computers using the following odbc profile...
>>
>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_works]
>> "Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 9\\win32\\dbodbc9.dll"
>> "UID"="dba"
>> "PWD"="*********"
>> "DatabaseName"="albatross"
>> "EngineName"="\\\\07-06-tides\\albatross_00"
>> "AutoStop"="Yes"
>> "Integrated"="No"
>> "Debug"="No"
>> "DisableMultiRowFetch"="No"
>> "CommLinks"="SharedMemory,TCPIP{},SPX{},NamedPipes"
>> "Compress"="No"
>> "Description"="DB"
>>
>> I recently updated the database server to SQL Anywhere 11.  I can connect 
>> to the database on the server itself, but if a client trys to connect 
>> using the following SQL Anywhere 11 odbc profile, I get a "Database 
>> server not found" error.
>>
>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
>> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
>> "UserID"="dba"
>> "Password"="********"
>> "ServerName"="\\\\07-06-tides\\albatross_00"
>> "AutoStop"="YES"
>> "Integrated"="NO"
>> "Debug"="NO"
>> "DisableMultiRowFetch"="NO"
>> "CommLinks"="SharedMemory,TCPIP{}"
>> "Compress"="NO"
>> "Description"="DB"
>> "DatabaseName"="albatross"
>>
>> I can connect to the server just fine if I use the ASA 9 odbc profile. 
>> But for some reason the SQL Anywhere 11 profile won't work.  What am I 
>> missing? I'm using version 11.0.1.2044.
>>
>> Thanks.
>>
>> Shenn Sellers
>>
>>
>
> 


0
Nick
9/15/2009 5:18:57 PM
I've attached the two log files and here is how I set up our server on a PC 
named 07-06-tides.

dbsvc -as -s auto -t network -w Albatross_DB 
C:\_Apps\Albatross\Bin32\dbsrv11.exe -n albatross_00 -c 20m 
C:\_Apps\Albatross\albatross.db


"Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in 
message news:4aafcc81$1@forums-1-dub...
> Also adding
>      "a -z -o filename.txt"
> to the servers will capture the context
> on that side as well.
>
> "Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in
> message news:4aafcbed$1@forums-1-dub...
>> While we sometimes see server names like that
>> this usage
>>
>>     "EngineName"="\\\\07-06-tides\\albatross_00"
>>
>> sometimes indicate a flawed configuraton there. When
>> you start the server, what -n switches do you use?
>> [in fact show you entire start line or service parameters]
>>
>> By specifying DEBUG=Yes and LOG=filename.txt
>> for both you can maybe capture the context of the
>> way the succeeding connection works and be able to
>> compare those. [actually debug= is historical and
>> ignored in both versions I believe, you just need
>> LOG=filename.txt for it to work]
>>
>> Also watch our for any asasrv.ini and sasrv.ini
>> files since they do interact here.
>>
>>
>>
>> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message
>> news:4aafc26f$1@forums-1-dub...
>>> Our database server was running under ASA 9 and we were connecting from
>>> client computers using the following odbc profile...
>>>
>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_works]
>>> "Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 9\\win32\\dbodbc9.dll"
>>> "UID"="dba"
>>> "PWD"="*********"
>>> "DatabaseName"="albatross"
>>> "EngineName"="\\\\07-06-tides\\albatross_00"
>>> "AutoStop"="Yes"
>>> "Integrated"="No"
>>> "Debug"="No"
>>> "DisableMultiRowFetch"="No"
>>> "CommLinks"="SharedMemory,TCPIP{},SPX{},NamedPipes"
>>> "Compress"="No"
>>> "Description"="DB"
>>>
>>> I recently updated the database server to SQL Anywhere 11.  I can 
>>> connect
>>> to the database on the server itself, but if a client trys to connect
>>> using the following SQL Anywhere 11 odbc profile, I get a "Database
>>> server not found" error.
>>>
>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
>>> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
>>> "UserID"="dba"
>>> "Password"="********"
>>> "ServerName"="\\\\07-06-tides\\albatross_00"
>>> "AutoStop"="YES"
>>> "Integrated"="NO"
>>> "Debug"="NO"
>>> "DisableMultiRowFetch"="NO"
>>> "CommLinks"="SharedMemory,TCPIP{}"
>>> "Compress"="NO"
>>> "Description"="DB"
>>> "DatabaseName"="albatross"
>>>
>>> I can connect to the server just fine if I use the ASA 9 odbc profile.
>>> But for some reason the SQL Anywhere 11 profile won't work.  What am I
>>> missing? I'm using version 11.0.1.2044.
>>>
>>> Thanks.
>>>
>>> Shenn Sellers
>>>
>>>
>>
>>
>
> 


begin 666 ASA9.log
M#0I4=64@4V5P(#$U(#(P,#D@,3 Z-# Z-34-"C$P.C0P.C4U($%P<&QI8V%T
M:6]N(&EN9F]R;6%T:6]N.@T*,3 Z-# Z-34@(DA/4U0],#8M.#D[3U,]5VEN
M9&]W<R!84"!"=6EL9" R-C P(%-E<G9I8V4@4&%C:R S.U!)1#TP>#,Q8SM4
M2%)%040],'AC.#0[15A%/4,Z7%=)3D1/5U-<<WES=&5M,S)<3T1"0T%$,S(N
M15A%.U9%4E-)3TX].2XP+C(N,C0U,3M!4$D]3T1"0SM424U%6D].14%$2E53
M5$U%3E0]+30R,"(-"C$P.C0P.C4U($%T=&5M<'1I;F<@=&\@8V]N;F5C="!U
M<VEN9SH-"E5)1#UD8F$[4%=$/2HJ*BHJ*BHJ.T1"3CUA;&)A=')O<W,[14Y'
M/5Q<,#<M,#8M=&ED97-<86QB871R;W-S7S P.T%35$]0/5E%4SM)3E0]3D\[
M1$)'/5E%4SM,3T<]0SI<7T%04%-<06QB871R;W-S7$QO9W-<05-!.2YL;V<[
M1$U21CU.3SM,24Y+4SU3:&%R961-96UO<GDL5$-025![?2Q34%A[?2Q.86UE
M9%!I<&5S.T-/35 ]3D\-"C$P.C0P.C4U($%T=&5M<'1I;F<@=&\@8V]N;F5C
M="!T;R!A(')U;FYI;F<@<V5R=F5R+BXN#0HQ,#HT,#HU-2!4<GEI;F<@=&\@
M<W1A<G0@4VAA<F5D365M;W)Y(&QI;FL@+BXN#0T*,3 Z-# Z-34@(" @(%-H
M87)E9$UE;6]R>2!L:6YK('-T87)T960@<W5C8V5S<V9U;&QY#0T*,3 Z-# Z
M-34@071T96UP=&EN9R!3:&%R961-96UO<GD@8V]N;F5C=&EO;B H;F\@87-A
M<W)V+FEN:2!C86-H960@861D<F5S<RD-#0HQ,#HT,#HU-2!&86EL960@=&\@
M8V]N;F5C="!O=F5R(%-H87)E9$UE;6]R>0T-"C$P.C0P.C4U(%)E;6]V:6YG
M(&9A:6QE9"!A9&1R97-S(&9R;VT@87-A<W)V+FEN:2!C86-H90T-"C$P.C0P
M.C4U(%1R>6EN9R!T;R!S=&%R="!40U!)4"!L:6YK("XN+@T-"C$P.C0P.C4U
M($QO861I;F<@=W-O8VLS,BYD;&P-"C$P.C0P.C4U($QO861I;F<@=W,R7S,R
M+F1L; T*,3 Z-# Z-34@5$-0('5S:6YG(%=I;G-O8VL@=F5R<VEO;B R+C -
M"C$P.C0P.C4U($UY($E0(&%D9')E<W,@:7,@,3 N,C N,C,P+C$Y-@T*,3 Z
M-# Z-34@37D@25 @861D<F5S<R!I<R Q,C<N,"XP+C$-"C$P.C0P.C4U(" @
M("!40U!)4"!L:6YK('-T87)T960@<W5C8V5S<V9U;&QY#0T*,3 Z-# Z-34@
M071T96UP=&EN9R!40U!)4"!C;VYN96-T:6]N("AA9&1R97-S(#$P+C(P+C(S
M,"XQ,3 Z,C8S."!F;W5N9"!I;B!A<V%S<G8N:6YI(&-A8VAE*0T-"C$P.C0P
M.C4U(%1R>6EN9R!T;R!F:6YD('-E<G9E<B!A="!C86-H960@861D<F5S<R Q
M,"XR,"XR,S N,3$P.C(V,S@@=VET:&]U="!B<F]A9&-A<W1I;F<-"C$P.C0P
M.C4U($9O=6YD('-E<G9E<BP@=F5R:69Y:6YG('-E<G9E<B!N86UE#0HQ,#HT
M,#HU-2!&;W5N9"!D871A8F%S92!S97)V97(@870@861D<F5S<R Q,"XR,"XR
M,S N,3$P.C(V,S@-"C$P.C0P.C4U($9O=6YD(&1A=&%B87-E('-E<G9E<B!A
M;&)A=')O<W-?,# @;VX@5$-025 @;&EN:PT*,3 Z-# Z-34@0V]N;F5C=&5D
M('1O('-E<G9E<B!O=F5R(%1#4$E0(&%T(&%D9')E<W,@,3 N,C N,C,P+C$Q
M,#HR-C,X#0T*,3 Z-# Z-34@0V]N;F5C=&5D('1O($%302!%;F=I;F4@=F5R
M<VEO;B Q,2XP+C$N,C T- T*,3 Z-# Z-34@0V]N;F5C=&5D('1O('1H92!S
M97)V97(L(&%T=&5M<'1I;F<@=&\@8V]N;F5C="!T;R!A(')U;FYI;F<@9&%T
M86)A<V4N+BX-"C$P.C0P.C4U(%L@(" V,UT@0V]N;F5C=&5D('1O(&1A=&%B
M87-E('-U8V-E<W-F=6QL>0T*,3 Z-# Z-34@6R @(#8S72!#;&EE;G0@9&ES
+8V]N;F5C=&5D#0H`
`
end

begin 666 sql11.log
M#0I4=64@4V5P(#$U(#(P,#D@,3 Z-#$Z,#4-"C$P.C0Q.C U($%T=&5M<'1I
M;F<@=&\@8V]N;F5C="!U<VEN9SH-"E5)1#UD8F$[4%=$/2HJ*BHJ*BHJ.T1"
M3CUA;&)A=')O<W,[14Y'/5Q<,#<M,#8M=&ED97-<86QB871R;W-S7S P.T%3
M5$]0/5E%4SM$4TX]86QB871R;W-S7S P.TE.5#U.3SM$0D<]6453.TQ/1SU#
M.EQ?05!04UQ!;&)A=')O<W-<3&]G<UQS<6PQ,2YL;V<[1$U21CU.3SM,24Y+
M4STG4VAA<F5D365M;W)Y+%1#4$E0>WTG.T-/35 ]3D\-"C$P.C0Q.C U($%T
M=&5M<'1I;F<@=&\@8V]N;F5C="!T;R!A(')U;FYI;F<@<V5R=F5R+BXN#0HQ
M,#HT,3HP-2!4<GEI;F<@=&\@<W1A<G0@4VAA<F5D365M;W)Y(&QI;FL@+BXN
M#0HQ,#HT,3HP-2 @(" @4VAA<F5D365M;W)Y(&QI;FL@<W1A<G1E9"!S=6-C
M97-S9G5L;'D-"C$P.C0Q.C U($%T=&5M<'1I;F<@4VAA<F5D365M;W)Y(&-O
M;FYE8W1I;VX@*&YO('-A<W)V+FEN:2!C86-H960@861D<F5S<RD-"C$P.C0Q
M.C U($9A:6QE9"!T;R!C;VYN96-T(&]V97(@4VAA<F5D365M;W)Y#0HQ,#HT
M,3HP-2!4<GEI;F<@=&\@<W1A<G0@5$-025 @;&EN:R N+BX-"C$P.C0Q.C U
M(%1#4"!U<VEN9R!7:6YS;V-K('9E<G-I;VX@,BXR#0HQ,#HT,3HP-B!->2!)
M4"!A9&1R97-S(&ES(#$P+C(P+C(S,"XQ.38-"C$P.C0Q.C V($UY($E0(&%D
M9')E<W,@:7,@,3(W+C N,"XQ#0HQ,#HT,3HP-B @(" @5$-025 @;&EN:R!S
M=&%R=&5D('-U8V-E<W-F=6QL>0T*,3 Z-#$Z,#8@071T96UP=&EN9R!40U!)
M4"!C;VYN96-T:6]N("AN;R!S87-R=BYI;FD@8V%C:&5D(&%D9')E<W,I#0HQ
M,#HT,3HP-B!,;V]K:6YG(&9O<B!S97)V97(@=VET:"!N86UE(%Q<,#<M,#8M
M=&ED97-<86QB871R;W-S7S P#0HQ,#HT,3HP-B!396YD:6YG(&)R;V%D8V%S
M="!T;R!F:6YD('-E<G9E<@T*,3 Z-#$Z,#8@57-I;F<@8G)O861C87-T(&%D
M9')E<W,@;V8Z(#$P+C(P+C(S,"XR-34Z,C8S. T*,3 Z-#$Z,#8@4V5N9&EN
M9R!B<F]A9&-A<W0@=&\@9FEN9"!S97)V97(-"C$P.C0Q.C V(%5S:6YG(&)R
M;V%D8V%S="!A9&1R97-S(&]F.B Q,C<N,C4U+C(U-2XR-34Z,C8S. T*,3 Z
M-#$Z,#<@4F5S96YD:6YG#0HQ,#HT,3HP."!297-E;F1I;F<-"C$P.C0Q.C Y
M(%)E<V5N9&EN9PT*,3 Z-#$Z,3 @4F5S96YD:6YG#0HQ,#HT,3HQ,2!297-E
M;F1I;F<-"C$P.C0Q.C$R(" @("!397)V97(@;F]T(&9O=6YD("AN;R!R97!L
M>2!R96-E:79E9"D-"C$P.C0Q.C$R($9A:6QE9"!T;R!C;VYN96-T(&]V97(@
M5$-025 -"C$P.C0Q.C$R($YO="!A='1E;7!T:6YG('1O(&%U=&]S=&%R="!S
J97)V97(-"C$P.C0Q.C$R($-A;FYO="!C;VYN96-T('1O('-E<G9E<@T*
`
end

0
Shenn
9/15/2009 5:46:05 PM
Nick,

After looking over the logs and trying things out, I've got it working with 
the following configuration.

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
"Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
"UserID"="dba"
"Password"="sql"
"ServerName"="albatross_00"
"AutoStop"="YES"
"Integrated"="NO"
"Debug"="NO"
"DisableMultiRowFetch"="NO"
"CommLinks"="SharedMemory,TCPIP{}"
"Compress"="NO"
"Description"="DB"
"DatabaseName"="albatross"

By taking out the computer name , "07-06-tides", under the "ServerName" 
entry, that corrected my problem.  Was I just doing it wrong this whole time 
or did you have to put the computer name in as well using ASA 9?  I've been 
doing it that way with ASA 9 for years.  Maybe SQLAny 11 just makes you do 
it the right way now.  Thanks for your help.


"Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message 
news:4aafd2dd$1@forums-1-dub...
> I've attached the two log files and here is how I set up our server on a 
> PC named 07-06-tides.
>
> dbsvc -as -s auto -t network -w Albatross_DB 
> C:\_Apps\Albatross\Bin32\dbsrv11.exe -n albatross_00 -c 20m 
> C:\_Apps\Albatross\albatross.db
>
>
> "Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in 
> message news:4aafcc81$1@forums-1-dub...
>> Also adding
>>      "a -z -o filename.txt"
>> to the servers will capture the context
>> on that side as well.
>>
>> "Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in
>> message news:4aafcbed$1@forums-1-dub...
>>> While we sometimes see server names like that
>>> this usage
>>>
>>>     "EngineName"="\\\\07-06-tides\\albatross_00"
>>>
>>> sometimes indicate a flawed configuraton there. When
>>> you start the server, what -n switches do you use?
>>> [in fact show you entire start line or service parameters]
>>>
>>> By specifying DEBUG=Yes and LOG=filename.txt
>>> for both you can maybe capture the context of the
>>> way the succeeding connection works and be able to
>>> compare those. [actually debug= is historical and
>>> ignored in both versions I believe, you just need
>>> LOG=filename.txt for it to work]
>>>
>>> Also watch our for any asasrv.ini and sasrv.ini
>>> files since they do interact here.
>>>
>>>
>>>
>>> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message
>>> news:4aafc26f$1@forums-1-dub...
>>>> Our database server was running under ASA 9 and we were connecting from
>>>> client computers using the following odbc profile...
>>>>
>>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_works]
>>>> "Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 
>>>> 9\\win32\\dbodbc9.dll"
>>>> "UID"="dba"
>>>> "PWD"="*********"
>>>> "DatabaseName"="albatross"
>>>> "EngineName"="\\\\07-06-tides\\albatross_00"
>>>> "AutoStop"="Yes"
>>>> "Integrated"="No"
>>>> "Debug"="No"
>>>> "DisableMultiRowFetch"="No"
>>>> "CommLinks"="SharedMemory,TCPIP{},SPX{},NamedPipes"
>>>> "Compress"="No"
>>>> "Description"="DB"
>>>>
>>>> I recently updated the database server to SQL Anywhere 11.  I can 
>>>> connect
>>>> to the database on the server itself, but if a client trys to connect
>>>> using the following SQL Anywhere 11 odbc profile, I get a "Database
>>>> server not found" error.
>>>>
>>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
>>>> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
>>>> "UserID"="dba"
>>>> "Password"="********"
>>>> "ServerName"="\\\\07-06-tides\\albatross_00"
>>>> "AutoStop"="YES"
>>>> "Integrated"="NO"
>>>> "Debug"="NO"
>>>> "DisableMultiRowFetch"="NO"
>>>> "CommLinks"="SharedMemory,TCPIP{}"
>>>> "Compress"="NO"
>>>> "Description"="DB"
>>>> "DatabaseName"="albatross"
>>>>
>>>> I can connect to the server just fine if I use the ASA 9 odbc profile.
>>>> But for some reason the SQL Anywhere 11 profile won't work.  What am I
>>>> missing? I'm using version 11.0.1.2044.
>>>>
>>>> Thanks.
>>>>
>>>> Shenn Sellers
>>>>
>>>>
>>>
>>>
>>
>>
>
>
> 


0
Shenn
9/15/2009 6:13:56 PM
That is consistent with the log from the v9 client trace as well

    10:40:55 Attempting TCPIP connection (address 10.20.230.110:2638 found 
in asasrv.ini cache)
   10:40:55 Trying to find server at cached address 10.20.230.110:2638 
without broadcasting
   10:40:55 Found server, verifying server name
   10:40:55 Found database server at address 10.20.230.110:2638
   10:40:55 Found database server albatross_00 on TCPIP link

It seems to just (silently) ignore the prefix with V9.
The fact that it worked before is actually a (silent)
bug I believe.  The server name was never meant
to be a system or domain name ... just one known
locally to the dbsrv process internally.


Glad to see you're up and running now

"Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message 
news:4aafd964@forums-1-dub...
> Nick,
>
> After looking over the logs and trying things out, I've got it working 
> with the following configuration.
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
> "UserID"="dba"
> "Password"="sql"
> "ServerName"="albatross_00"
> "AutoStop"="YES"
> "Integrated"="NO"
> "Debug"="NO"
> "DisableMultiRowFetch"="NO"
> "CommLinks"="SharedMemory,TCPIP{}"
> "Compress"="NO"
> "Description"="DB"
> "DatabaseName"="albatross"
>
> By taking out the computer name , "07-06-tides", under the "ServerName" 
> entry, that corrected my problem.  Was I just doing it wrong this whole 
> time or did you have to put the computer name in as well using ASA 9? 
> I've been doing it that way with ASA 9 for years.  Maybe SQLAny 11 just 
> makes you do it the right way now.  Thanks for your help.
>
>
> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message 
> news:4aafd2dd$1@forums-1-dub...
>> I've attached the two log files and here is how I set up our server on a 
>> PC named 07-06-tides.
>>
>> dbsvc -as -s auto -t network -w Albatross_DB 
>> C:\_Apps\Albatross\Bin32\dbsrv11.exe -n albatross_00 -c 20m 
>> C:\_Apps\Albatross\albatross.db
>>
>>
>> "Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in 
>> message news:4aafcc81$1@forums-1-dub...
>>> Also adding
>>>      "a -z -o filename.txt"
>>> to the servers will capture the context
>>> on that side as well.
>>>
>>> "Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in
>>> message news:4aafcbed$1@forums-1-dub...
>>>> While we sometimes see server names like that
>>>> this usage
>>>>
>>>>     "EngineName"="\\\\07-06-tides\\albatross_00"
>>>>
>>>> sometimes indicate a flawed configuraton there. When
>>>> you start the server, what -n switches do you use?
>>>> [in fact show you entire start line or service parameters]
>>>>
>>>> By specifying DEBUG=Yes and LOG=filename.txt
>>>> for both you can maybe capture the context of the
>>>> way the succeeding connection works and be able to
>>>> compare those. [actually debug= is historical and
>>>> ignored in both versions I believe, you just need
>>>> LOG=filename.txt for it to work]
>>>>
>>>> Also watch our for any asasrv.ini and sasrv.ini
>>>> files since they do interact here.
>>>>
>>>>
>>>>
>>>> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message
>>>> news:4aafc26f$1@forums-1-dub...
>>>>> Our database server was running under ASA 9 and we were connecting 
>>>>> from
>>>>> client computers using the following odbc profile...
>>>>>
>>>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_works]
>>>>> "Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 
>>>>> 9\\win32\\dbodbc9.dll"
>>>>> "UID"="dba"
>>>>> "PWD"="*********"
>>>>> "DatabaseName"="albatross"
>>>>> "EngineName"="\\\\07-06-tides\\albatross_00"
>>>>> "AutoStop"="Yes"
>>>>> "Integrated"="No"
>>>>> "Debug"="No"
>>>>> "DisableMultiRowFetch"="No"
>>>>> "CommLinks"="SharedMemory,TCPIP{},SPX{},NamedPipes"
>>>>> "Compress"="No"
>>>>> "Description"="DB"
>>>>>
>>>>> I recently updated the database server to SQL Anywhere 11.  I can 
>>>>> connect
>>>>> to the database on the server itself, but if a client trys to connect
>>>>> using the following SQL Anywhere 11 odbc profile, I get a "Database
>>>>> server not found" error.
>>>>>
>>>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
>>>>> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
>>>>> "UserID"="dba"
>>>>> "Password"="********"
>>>>> "ServerName"="\\\\07-06-tides\\albatross_00"
>>>>> "AutoStop"="YES"
>>>>> "Integrated"="NO"
>>>>> "Debug"="NO"
>>>>> "DisableMultiRowFetch"="NO"
>>>>> "CommLinks"="SharedMemory,TCPIP{}"
>>>>> "Compress"="NO"
>>>>> "Description"="DB"
>>>>> "DatabaseName"="albatross"
>>>>>
>>>>> I can connect to the server just fine if I use the ASA 9 odbc profile.
>>>>> But for some reason the SQL Anywhere 11 profile won't work.  What am I
>>>>> missing? I'm using version 11.0.1.2044.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Shenn Sellers
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
> 


0
Nick
9/15/2009 7:38:50 PM
It's not so much a bug in v9 as an enhancement in v10, though I suppose 
arguments can be made either way. In the version 9 client, we parsed the 
server name and if any / or \ characters were found, we interpreted it 
as a fully-qualified filename and used the last element of the name 
minus the extension as the server name. In this case, we would convert 
"ENG=\\\\07-06-tides\\albatross_00" into "ENG=albatross_00", which 
explained why it worked. According to the comments in this routine, this 
is a hold-over from Watcom SQL version 4, which I believe was released 
sometime in the late 1840's.

In v10, we dropped this odd behaviour, so the engine name we searched 
for was "\\\\07-06-tides\\albatross_00", which obviously doesn't match 
the server's actual name.

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community
    http://www.sybase.com/developer/library/sql-anywhere-techcorner
SQL Anywhere Blog Center
    http://www.sybase.com/sqlanyblogs


Nick Elson [Sybase iAnywhere] wrote:
> That is consistent with the log from the v9 client trace as well
> 
>     10:40:55 Attempting TCPIP connection (address 10.20.230.110:2638 found 
> in asasrv.ini cache)
>    10:40:55 Trying to find server at cached address 10.20.230.110:2638 
> without broadcasting
>    10:40:55 Found server, verifying server name
>    10:40:55 Found database server at address 10.20.230.110:2638
>    10:40:55 Found database server albatross_00 on TCPIP link
> 
> It seems to just (silently) ignore the prefix with V9.
> The fact that it worked before is actually a (silent)
> bug I believe.  The server name was never meant
> to be a system or domain name ... just one known
> locally to the dbsrv process internally.
> 
> 
> Glad to see you're up and running now
> 
> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message 
> news:4aafd964@forums-1-dub...
>> Nick,
>>
>> After looking over the logs and trying things out, I've got it working 
>> with the following configuration.
>>
>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
>> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
>> "UserID"="dba"
>> "Password"="sql"
>> "ServerName"="albatross_00"
>> "AutoStop"="YES"
>> "Integrated"="NO"
>> "Debug"="NO"
>> "DisableMultiRowFetch"="NO"
>> "CommLinks"="SharedMemory,TCPIP{}"
>> "Compress"="NO"
>> "Description"="DB"
>> "DatabaseName"="albatross"
>>
>> By taking out the computer name , "07-06-tides", under the "ServerName" 
>> entry, that corrected my problem.  Was I just doing it wrong this whole 
>> time or did you have to put the computer name in as well using ASA 9? 
>> I've been doing it that way with ASA 9 for years.  Maybe SQLAny 11 just 
>> makes you do it the right way now.  Thanks for your help.
>>
>>
>> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message 
>> news:4aafd2dd$1@forums-1-dub...
>>> I've attached the two log files and here is how I set up our server on a 
>>> PC named 07-06-tides.
>>>
>>> dbsvc -as -s auto -t network -w Albatross_DB 
>>> C:\_Apps\Albatross\Bin32\dbsrv11.exe -n albatross_00 -c 20m 
>>> C:\_Apps\Albatross\albatross.db
>>>
>>>
>>> "Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in 
>>> message news:4aafcc81$1@forums-1-dub...
>>>> Also adding
>>>>      "a -z -o filename.txt"
>>>> to the servers will capture the context
>>>> on that side as well.
>>>>
>>>> "Nick Elson [Sybase iAnywhere]" <@nick@.@elson@@sybase@.@com@> wrote in
>>>> message news:4aafcbed$1@forums-1-dub...
>>>>> While we sometimes see server names like that
>>>>> this usage
>>>>>
>>>>>     "EngineName"="\\\\07-06-tides\\albatross_00"
>>>>>
>>>>> sometimes indicate a flawed configuraton there. When
>>>>> you start the server, what -n switches do you use?
>>>>> [in fact show you entire start line or service parameters]
>>>>>
>>>>> By specifying DEBUG=Yes and LOG=filename.txt
>>>>> for both you can maybe capture the context of the
>>>>> way the succeeding connection works and be able to
>>>>> compare those. [actually debug= is historical and
>>>>> ignored in both versions I believe, you just need
>>>>> LOG=filename.txt for it to work]
>>>>>
>>>>> Also watch our for any asasrv.ini and sasrv.ini
>>>>> files since they do interact here.
>>>>>
>>>>>
>>>>>
>>>>> "Shenn Sellers" <ssellers@co.riverside.ca.us> wrote in message
>>>>> news:4aafc26f$1@forums-1-dub...
>>>>>> Our database server was running under ASA 9 and we were connecting 
>>>>>> from
>>>>>> client computers using the following odbc profile...
>>>>>>
>>>>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_works]
>>>>>> "Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 
>>>>>> 9\\win32\\dbodbc9.dll"
>>>>>> "UID"="dba"
>>>>>> "PWD"="*********"
>>>>>> "DatabaseName"="albatross"
>>>>>> "EngineName"="\\\\07-06-tides\\albatross_00"
>>>>>> "AutoStop"="Yes"
>>>>>> "Integrated"="No"
>>>>>> "Debug"="No"
>>>>>> "DisableMultiRowFetch"="No"
>>>>>> "CommLinks"="SharedMemory,TCPIP{},SPX{},NamedPipes"
>>>>>> "Compress"="No"
>>>>>> "Description"="DB"
>>>>>>
>>>>>> I recently updated the database server to SQL Anywhere 11.  I can 
>>>>>> connect
>>>>>> to the database on the server itself, but if a client trys to connect
>>>>>> using the following SQL Anywhere 11 odbc profile, I get a "Database
>>>>>> server not found" error.
>>>>>>
>>>>>> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\albatross_00]
>>>>>> "Driver"="C:\\PROGRA~1\\SQLANY~2\\Bin32\\dbodbc11.dll"
>>>>>> "UserID"="dba"
>>>>>> "Password"="********"
>>>>>> "ServerName"="\\\\07-06-tides\\albatross_00"
>>>>>> "AutoStop"="YES"
>>>>>> "Integrated"="NO"
>>>>>> "Debug"="NO"
>>>>>> "DisableMultiRowFetch"="NO"
>>>>>> "CommLinks"="SharedMemory,TCPIP{}"
>>>>>> "Compress"="NO"
>>>>>> "Description"="DB"
>>>>>> "DatabaseName"="albatross"
>>>>>>
>>>>>> I can connect to the server just fine if I use the ASA 9 odbc profile.
>>>>>> But for some reason the SQL Anywhere 11 profile won't work.  What am I
>>>>>> missing? I'm using version 11.0.1.2044.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Shenn Sellers
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
> 
> 
0
Graeme
9/16/2009 2:34:41 PM
Reply:

Similar Artilces:

DataBase Migration from ASA 9.02 To SQLANYWHERE 11.01
Hello all...We are migrating our Sybase ASA Database from ASA 9.02 to SQLANYWHERE 11.0.1. Everything seems to be going well except for a series of errors I am getting when I run the reload.sql file from the DOS prompt. I am getting a warning or error that states: "Procedure 'ml_add_property' not found SQLCODE=-265, ODBC 3 State="42S02" CALL dbo.ml_add_property( 'SIS', 'Carrier(Bell Mobility 1x)', 'enable', 'yes' ) After doing some research, I believe that ...

DataBase Migration from ASA 9.02 To SQLANYWHERE 11.01
Hello all... I hope this is the right forum to ask the following question: We are migrated our Sybase ASA Database from ASA 9.02 to SQLAnyWhere 11.01. Everything seems to be going well except a series of errors I am getting when I run the reload.sql file from the DOS prompt. I am getting a warning or error that states: "Procedure 'ml_add_property' not found SQLCODE=-265, ODBC 3 State="42S02" CALL dbo.ml_add_property( 'SIS', 'Carrier(Bell Mobility 1x)', 'enable', 'yes' ) Any clue as to what thi...

sqlanywhere and sqlanywhere server
Currently i am using sqlanywhere and powerbuilder tool as my system development. And i am developing a standalone system. Let say, if i want to migrate my standalone system to client-server system, how do i do that? I heard that i need to have sqlanywhere(server engine) to deploy my system as client-server system. If so, do i need to install sqlanywhere(server engine) into window NT or just normal pc(treat as server). For client-server system, do i need to install sqlanywhere server at server and sqlanywhere client as normal pc where my program is installed? Could someone tell me where...

getting error after upgrading from sqlanywhere 7 to sqlanywhere 9
i'm using sybase sql server any where 7 and by using dbsrv7.exe i'm able to create db. it's working fine. no issues. now i'm upgrading to sybase sql server any where 9 and by using dbsrv9.exe i created db. this time when i'm using sysindexes table of sybase i'm getting error as Table name 'sysindexes' is ambiguous exception com.sybase.jdbc2.jdbc.SybSQLException because ASA Error -852: Table name 'sysindexes' is ambiguous com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -852: Table name 'sysindexes' is ambiguous at com.sybase.jdbc2...

upgrade path to asa from sqlanywhere server
hi, what are my upgrade options in moving from v5 sqlanywhere server to asa? price? john cummings >what are my upgrade options in moving from v5 sqlanywhere server to asa? >price? The best places to find price information are: www.sybase.com Your sybase sales rep Various discount software houses. Regards Leo Tohill - Team Powersoft -- Please post in newsgroup, not via email < ...

Upgrade SqlAnywhere Server 5.0 auf SqlAnywhere 7.0
Hello, We want to upgrade our SqlAnywhere database server from 5.0 to 7.0. How does this work? Please help me. Many thanks, Gerhard You can either unload/reload or upgrade the database. The documentation discusses this. BTW ASA7 is currently in limited support. Current versions are ASA8 and ASA9 so it would be wise to consider going to a later version. <Gerhard> wrote in message news:41e3a189.7488.1681692777@sybase.com... > Hello, > We want to upgrade our SqlAnywhere database server from 5.0 > to 7.0. How does this work? Please help me. > > Many th...

Unable to start database server in SQLANYWHERE 11.
I am trying to create a new database in SQL ANYWHERE 11.0.1 and I am getting the following errors using the Create Database Wizard and I am getting the following errors: Unable to start database server [Sybase][ODBC Driver][SQL Anywhere]Unable to start database server Error code=-80 SQL state=08001 Any clue as to what might be causing this? ...

Database server not found with ASA 9.0.1
We have been running a database using ASA 8.0.3.5182 running on a Mandrake 10.1 system. I am using unixODBC 2.2.8. I have just installed ASA 9.0.1.1989 and am trying to get the ODBC connections to work but keep getting a "Database server not found error". What I have done so far is just create the entries in the odbcinst.ini and odbc.ini files. The database is still running on the 8.0.3 engine. Whenever I try to connect using the 9.0.1 libraries, it fails but if I switch back to the 8.0.3 libraries, everything works. I am able to connect to the database from a...

Migrating ASA 9.03 to SQLAnyWhere 11.0.1
Hello all...I am migrating our Sybase ASA databases from ASA 9.03 to SQLAnyWhere 11.0.1. I have noticed that I must use double quotes in columns which are reserved words in order to prevent any syntax errors when executing the SQL. This works quite well in ISQL 11.0.1 but when I try to use the double quotes in datawindow object, say: SELECT "opinions"."opinion_number", "opinions"."date_recieved", "opinions"."from", "opinions"."responsible_attorney_id", "opinion...

Migrating DB from Adaptive Server Anywhere 9.0.2 to SqlAnyWhere 11
Hi, We are trying to convert our application to 11.5.1, which was recently converted to 10.5.2 from 9.0. When I try to create an ODBC driver in SQLAnywhere 11 pointing to our DB from 10.5.2, it says the dB was created in an earlier version. How to I migrate my DB to the newer version. Thanks Subhash The SQL Anywhere that is installed with PowerBuilder is a developer's edition -- you are only licensed to deploy the runtime edition of SQL Anywhere (rtengX.exe where X is the version of SA) unless you obtain licenses for the other components. The migration (upgrading) p...

Problem Upgrading SQLAnywhere 5.5 Databases to ASA 6.0.1
I have a few small databases in SQLAnywhere 5.5 Since I don't have the driver or server available I wanted to convert them to ASA 6.0.1 However, the upgrade utility in Sybase Central 3.1.0 reports that the databases are not a valid ASA database file. Is this a bug or am I missing something here? ...

Migration from SQLAnywhere 10 to SQLAnywhere 11
Do I need to migrate the database file if i want to migrate my application from SQLAnywhere 10 to SQLAnywhere 11? or a databse file created by SQLAnywhere10 will run fine under SQLAnywhere 11? Jorge, From: http://dcx.sybase.com/index.php#http%3A%2F%2Fdcx.sybase.com%2F1100en%2Fsachanges_en11%2Fv10upgrade-up-sql-any-123456.html ======== Upgrading version 10.0.0 and later databases If you are upgrading from version 10.0.0 or later, you can either use the Upgrade utility or rebuild your database. Upgrading or rebuilding is an optional step because the version 11 software ...

Upgrade from 11.0.3.3 SQL Server to 11.9.2 with RepServer 11.5
I am preparing to upgrade our production servers (11.0.3.3) using RepServer 11.5 with LTMs. My understanding is that the ASE 11.9.2 has RepAgents build in as Open Server applications. Are there any issues with upgrading that I need to be aware of? Where would I look? I would assume that I don't need to run LTMs anymore, but I need to ensure no loss of replication to the warm standby. Any advice? Take care. JCS ...

SQLAnyWhere Database Server
Actually I sent this inquiry to the sqlanywhere.general newsgroup but I think that this is also related to this newsgroup. So, I am sending this also. Please excuse me just this once. Here is my question: How do you connect, in PowerBuilder, to a SQL AnyWhere database server without it running as yet? Use the sample database configuration as an example. Basically, check the "Automatically start the database if it isn't running". However, this only will only start an engine on the same machine. "Ben Lahoy" <blahoy@datavantage.com> wrote in messa...

Web resources about - Database Server not found after upgrade from ASA 9 to SQLAnywhere 11 - sybase.sqlanywhere.general

IBM Tivoli Storage Manager - Wikipedia, the free encyclopedia
IBM Tivoli Storage Manager ( TSM or ITSM ) is a centralized, policy-based, enterprise class, data backup and recovery package. The software enables ...

Archives - Caelum's Blog
Caelum's Blog Random Stuff Navigation Home - Articles Tags 256colors 64 64bit 8 activeperl activestate advent ajax alsa amd64 asa asus automation ...

keynote bingo - Google Search
Search Images Maps Play YouTube News Gmail Drive More Calendar Translate Mobile Books Wallet Shopping Blogger Finance Photos Videos Even more ...

Mobile and Wireless Partners - Partners - Sybase Inc
Thanks for visiting the Partners section of Sybase.com. Here you will find information about Mobile and Wireless Partners - Partners. For more ...

Datensynchronisierung - sqlanywhere
„Good Partner - quick and reliable answers! Fast "delivery" by Email. Everybody can count on them." Tímea Steigervald, Product Manager Kvazar-Micro ...

Browse file extension list beginning with letter A
Browse file extension list beginning with letter A - File-Extensions.org search page

OpenLink ODBC Adapter for Ruby on Rails: OpenLink ODBC Adapter for Ruby on Rails: Downloads
OpenLink ODBC Adapter for Ruby on Rails: OpenLink ODBC Adapter for Ruby on Rails: Downloads

Developer Edition - sqlanywhere
„Good Partner - quick and reliable answers! Fast "delivery" by Email. Everybody can count on them." Tímea Steigervald, Product Manager Kvazar-Micro ...

IBM - sqlanywhere
„Good Partner - quick and reliable answers! Fast "delivery" by Email. Everybody can count on them." Tímea Steigervald, Product Manager Kvazar-Micro ...

Datenaustausch - sqlanywhere
„Good Partner - quick and reliable answers! Fast "delivery" by Email. Everybody can count on them." Tímea Steigervald, Product Manager Kvazar-Micro ...

Resources last updated: 12/9/2015 2:57:59 PM