Re: VB6 apps cannot connect to SQL2000
From: NewDBAGuy (NewDBAGuy_at_discussions.microsoft.com)
Date: 11/26/04
- Next message: Thirumalai Internal: "Problem in installing SQLSERVER2000 Developer Edition"
- Previous message: Scott Morris: "Re: DB-Library and sp_dbcmptlevel in Sql Server 2005"
- In reply to: Stephen Gartrell: "Re: VB6 apps cannot connect to SQL2000"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 26 Nov 2004 06:23:02 -0800
Thanks for the reply. I did recreate the logins on SQL, and was able to
verify that Enterprise Manager could connect with these logins.
It turned out that the old server had NWLink IPX/SPX installed, and the new
one did not. The VB apps' connection strings were hard coded to reference the
IPX library. I was able to edit the applications, remove the portion of the
strings that wanted to use IPX, and they connected fine.
Our company's policy is not to install IPX on new Windows servers. In this
case, I was able to fix the issue without having to ask for an exception.
"Stephen Gartrell" wrote:
> I've seen issues when detaching a database, copying it to new server, and
> attaching it there where subsequently user accounts (i.e., Sql Server
> logons) were not "synced" to individual database access privileges. Cured
> by dropping user access to the individual databases (if they should exist)
> and then re-adding the users with appropriate privs (e.g.,
> data_reader/data_writer).
>
> "NewDBAGuy" <NewDBAGuy@discussions.microsoft.com> wrote in message
> news:7B87081A-726B-44F2-AB1B-D7907C7A0BE9@microsoft.com...
> > I forgot to mention that the PCs I tested connectivity with previously had
> > MDAC 2.6 and the SQL7 client installed before I upgraded the SQL client to
> > 2000 version. They were able to connect through Enterprise Manager
> > afterwards, just not through these old VB6 applications. I don't have much
> > success trying to edit the apps for changes, since there are several
> > third-party controls referenced that I don't have installed.
> >
> > "NewDBAGuy" wrote:
> >
> > > I am working to replace our production SQL7 server on NT with a new box
> > > running SQL2000 with Win2k3. Last week I had prepped the new server by
> > > importing the db from backup, the jobs, DTS packages, and by (hopefully)
> > > restoring the user accounts - only 6 of them. The old and new servers
> are
> > > both configured for Mixed mode authentication. The old server is in a
> > > workgroup, but the new server is in an A.D. domain.
> > >
> > > Over the weekend I did a trial run to migrate to the new server. I took
> the
> > > old offline, renamed the new server to match the old, matched the IP
> address,
> > > and run sp_dropserver/sp_addserver, rebooted. An Access database we
> currently
> > > use with linked tables for reports was able to connect and pull data.
> > > Enterprise Manager was able to authenticate with different user
> accounts. But
> > > older VB6 applications never loaded correctly. I'm not a VB guy, but I
> did
> > > notice in their main Form_Load statement they try to connect to the
> server
> > > specifically by \\<servername> with a user ID and password hard-coded.
> I've
> > > got the user ID and password matched on the server, but they never
> connected.
> > > I checked the Client Network and Server Network utilites, and the server
> and
> > > a client both listed TCP/IP as active. Shouldn't that be enough to
> connect,
> > > or am I missing something?
> > >
> > > The clients run NT 4 sp6a. We're a Netware-based company, so we don't
> have
> > > user PCs joining a domain. Any help would be appreciated. I feel I am
> very
> > > close to being finished with this project.
>
>
>
- Next message: Thirumalai Internal: "Problem in installing SQLSERVER2000 Developer Edition"
- Previous message: Scott Morris: "Re: DB-Library and sp_dbcmptlevel in Sql Server 2005"
- In reply to: Stephen Gartrell: "Re: VB6 apps cannot connect to SQL2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
