I have made an 'interesting' development...
I have downloaded an evaluation copy of DataDirect's latest ODBC drivers. I
created a DSN connection and then allowed InterDev to access that connection
and create a connection string. I can now load my asp page with the new
connection string, which is...
"Provider=MSDASQL.1;Persist Security Info=False;User ID=sa;Data
Source=EMDDDodbc;Extended
Properties=""DSN=EMDDDodbc;UID=sa;NA=SDT02,5001;DB =EMD;"";User Id=sa;"
Your comments, Bob, about using the sa login are noted, and I particularly
appreciate the info about the slammer virus. Now that I am aware, I will
amend the login. When I have finished the website it will be moved to a
production server from my laptop and a new default login with password will
be assigned.
I am still left wondering why the Sybase OLE DB Provider does not work for
the asp page. Could it be a problem with my IIS settings?
Thanks for all the help and advice
"Bob Barrows [MVP]" <reb01501@NOyahoo.SPAMcom> wrote in message
news:OWQPfLCNEHA.3420@TK2MSFTNGP11.phx.gbl...[color=blue]
> Paul Robinson wrote:[color=green]
> > Aaron, thanks for your reply.
> > Looking at your advice in reverse order:
> >
> > The trial connection hangs just like all my other attempts.
> >
> > The code produced by InterDev for the connection string is
> > detailed below. As I have noted in my reply to advice from Steven
> > Burn, with this connection string InterDev rapidly accesses the
> > database and shows the data in the design ide.[/color]
>
> Different machine, different user account than the one that asp uses.
>[color=green]
> > My asp page code is OK
> > because I can open the page without any delay or problem if I change
> > the database to Access, where I have replicated the tables. Further,
> > if I comment out or remove any code relevant to the Sybase
> > connection, then the page loads OK. It is only when I attempt to open
> > the connection that the page hangs.I receive no error message, just a
> > blank page still trying to load, until I have tried to connect enough
> > times to generate the HTTP 403.9 error message. Sybase does not show
> > any connection coming through, so what is happening?[/color]
>
> It sounds as if your network is not finding the Sybase server (and is
> failing to time out ... very unusual)
>
> Have you tried searching the Sybase KB?
>
http://my.sybase.com/search_advanced
>
> More below:
>[color=green]
> >
> > This is the connection string generated by InterDev
> > Provider=Sybase.ASEOLEDBProvider.2;Initial Catalog=EMD;User ID=sa;[/color]
>
> Mistake #1 - never use the sa account for your applications! Create an
> account with limited permissions to be used by your apps. Protect the sa
> account as if your server/network/job depends on it - it does.
>[color=green]
> > Data
> > Source=EMDhome;[/color]
>
> Have you tried specifying the port number as described at able-consulting?
> Is this quote from able-consulting relevant?
> ************************************************** ********
> Note: The Open Client 12 Sybase OLE DB Provider fails to work without
> creating a Data Source .IDS file using the Sybase Data Administrator.
> These .IDS files resemble ODBC DSNs.
>
> Note: With Open Client 12.5, the server port number feature finally works,
> allowing fully qualified network connection strings to be used without
> defining any .IDS Data Source files.
>
> ************************************************** *********
>
>[color=green]
> > Extended Properties="";Server Name=SDT02;Network
> > Protocol=Winsock;Server Port Address=5001;HA Server Name="";HA Server
> > Port Address="";Character Set="";Language="";Application
> > Name="";Optimize Prepare=Partial;Select Method=Direct;Raise Error
> > Behavior=MS Compatible;Print Statement Behavior=MS Compatible;Extended
> > ErrorInfo=TRUE;Stored Proc Row Count=Last Statement Only;WorkStation
> > ID="";Row Cache Size=50;Enable Quoted Identifiers=0;Packet
> > Size=1;Default Length For Long
> >[/color]
>[/color]
Data=1024;UseSybaseLDAP=False;SybaseLDAPURL="";Syb aseServerName=389;UseLDAPH[color=blue][color=green]
> > AServer=0;Use SSL=0;Trusted Root File Name="";Interfaces
> > File="";Interfaces File Server
> > Name="";EnableSPColumnTypes=True;TruncateTimeTypeF ractions=1[/color]
>
> A lot of these extended properties look like the defaults, and they can
> probably be eliminated from the connection string used by your[/color]
application.[color=blue]
>[color=green]
> >
> > These are the code extracts on my asp pages:
> >
> > Dim objConn, strConnect, objRS, strSQLproc
> > Set objConn = server.CreateObject("ADODB.Connection")
> > ' strConnect = Application("connEMD_ConnectionString")
> > ' strConnect = "Provider=Sybase.ASEOLEDBProvider.2;Data
> > Source=EMD;Server Name=SDT02;Network Protocol=Winsock;Server Port
> > Address=5001;User Id=sa;Password="[/color]
>
> I hope this does not mean your sa password is an empty string - have you
> never heard of the Slammer internet worm? It propogates by attack sql
> servers where the sa password is blank. Hopefully, you've just censored it
> for this newsgroup message.
>
>[color=green]
> > Dim arrOperators, iCount strSQLproc = "SELECT * FROM tblOperator"
> > ' strSQLproc = "EXECUTE procOperators1"
> > objConn.Open strConnect
> > Set objRS = objConn.Execute(strSQLproc)
> > arrOperators = objRS.GetRows
> > objConn.Close
> > Set objConn=Nothing
> > ...[/color]
>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"
>
>[/color]
