ODBC drivers needed

My server is running with 2003R2 x64 with SQL 2005. Some of my client
computers are having some issues with ODBC errors while working in an
accounting package. I have been told that it is most likely a driver
compatibility issue between the XP pro versions on the clients and the 64
bit version on my server.
I suppose first does this seem plausible, and where might I find the updated
drivers for XP? I am not sure if this is the correct forum for this request,
but it seemed to be the closest.
Many thanks in advance.
David
David (David@.Fidia.com) writes:
> My server is running with 2003R2 x64 with SQL 2005. Some of my client
> computers are having some issues with ODBC errors while working in an
> accounting package. I have been told that it is most likely a driver
> compatibility issue between the XP pro versions on the clients and the 64
> bit version on my server.
> I suppose first does this seem plausible, and where might I find the
> updated drivers for XP? I am not sure if this is the correct forum for
> this request, but it seemed to be the closest.
http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&DisplayLang=en
and
[url]http://www.microsoft.com/downloads/info.aspx?na=22&p=4&SrcDisplayLang=en&SrcCategoryI d=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFa milyID%3d7358da31-959c-4e3e-8115-51dc6d441365%26DisplayLang%3den[/url]
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

ODBC access errors

I have just rebuilt the boot drive of a PC used as a
server using MSDE 2000. It is running under Windows 2000
SP4.
Since the rebuild, anyone with less that administrator
priveliges on the local machine have been denied access to
the SQL server.
In the ODBC server DSN configration settings, attempting
to login produces SQL Server errors 11004 and 6, while
attempting to run the application attempting to access the
server gives errorcode 61440.
Any suggestions as to the cause of this problem will be
gratefully received.
Many thanks in advance.
Ian CoatesSorted. It appears the application makes use of the Guest account which was
disabled. Renabling it sorted the problem.
Ian Coates
"Ian Coates" <anonymous@.discussions.microsoft.com> wrote in message
news:433a01c47325$57138de0$a301280a@.phx.gbl...
> I have just rebuilt the boot drive of a PC used as a
> server using MSDE 2000. It is running under Windows 2000
> SP4.
> Since the rebuild, anyone with less that administrator
> priveliges on the local machine have been denied access to
> the SQL server.
> In the ODBC server DSN configration settings, attempting
> to login produces SQL Server errors 11004 and 6, while
> attempting to run the application attempting to access the
> server gives errorcode 61440.
> Any suggestions as to the cause of this problem will be
> gratefully received.
> Many thanks in advance.
> Ian Coates

ODBC access errors

I have just rebuilt the boot drive of a PC used as a
server using MSDE 2000. It is running under Windows 2000
SP4.
Since the rebuild, anyone with less that administrator
priveliges on the local machine have been denied access to
the SQL server.
In the ODBC server DSN configration settings, attempting
to login produces SQL Server errors 11004 and 6, while
attempting to run the application attempting to access the
server gives errorcode 61440.
Any suggestions as to the cause of this problem will be
gratefully received.
Many thanks in advance.
Ian Coates
Sorted. It appears the application makes use of the Guest account which was
disabled. Renabling it sorted the problem.
Ian Coates
"Ian Coates" <anonymous@.discussions.microsoft.com> wrote in message
news:433a01c47325$57138de0$a301280a@.phx.gbl...
> I have just rebuilt the boot drive of a PC used as a
> server using MSDE 2000. It is running under Windows 2000
> SP4.
> Since the rebuild, anyone with less that administrator
> priveliges on the local machine have been denied access to
> the SQL server.
> In the ODBC server DSN configration settings, attempting
> to login produces SQL Server errors 11004 and 6, while
> attempting to run the application attempting to access the
> server gives errorcode 61440.
> Any suggestions as to the cause of this problem will be
> gratefully received.
> Many thanks in advance.
> Ian Coates

Occasional record fails to merge replicate, but SQL Server reports no errors

Rob,
I have seen this happen in 2 circumstances:
(1) Firstly when the filter was set to 1=2 and inserts
were made while the merge agent was running
(2) Secondly, if you bulk insert the rows and choose the
defaults, then FIRE_TRIGGERS is false and consequently
the rows are not added to MSmerge_contents.
In either case, you need to run sp_addtabletocontents to
include the rows then resynchronise. Alternatively you
can use sp_mergedummyupdate for a single row.
For your case I'd first check to see if there are
corresponding records in MSmerge_contents - ie did the
triggers fire? This should help narrow things down.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul, thanks for the quick reply. I have no filters on the merge and do not
do any bulk inserts, but I will take your suggestion and review
msmerge_contents next time this occurs.
Rob Kraft
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:2dd801c4c0fd$22539b60$a601280a@.phx.gbl...
> Rob,
> I have seen this happen in 2 circumstances:
> (1) Firstly when the filter was set to 1=2 and inserts
> were made while the merge agent was running
> (2) Secondly, if you bulk insert the rows and choose the
> defaults, then FIRE_TRIGGERS is false and consequently
> the rows are not added to MSmerge_contents.
> In either case, you need to run sp_addtabletocontents to
> include the rows then resynchronise. Alternatively you
> can use sp_mergedummyupdate for a single row.
> For your case I'd first check to see if there are
> corresponding records in MSmerge_contents - ie did the
> triggers fire? This should help narrow things down.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>