| Author |
 Topic  |
|
|
large
Starting Member
8 Posts |
 Posted - March 02 2007 : 16:21:32
|
***Server 2003 64bit and SQL 2005 database issue***
I've previously install vpasp6 on a Win2k3 and SQL 2k with great success.
However, I'm trying to set up VPASP from scratch on a clean server (fresh install of everythinglimited configuration) and receive the following error when configuring the site with SQL...
ADODB.Connection error '800a0ea9'
Provider is not specified and there is no designated default provider.
/shop$db.asp, line 345
It’s as if the DB is not being communicated with.
Any help would be appreciated...
Thanks,
Dan
|
|
|
Kidd
VP-CART Super User
Australia
373 Posts |
Posted - March 09 2007 : 01:42:46
|
| i think sql2005 uses different connection string, you can try google |
 |
|
|
large
Starting Member
8 Posts |
Posted - March 09 2007 : 06:26:58
|
Thanks Kid,
I've searched high and low...
In doing some research, I've found that this may be a compatibility issue with products (OSx64, SQL2k5 x32, mdac/odbc/etc...) used. However, nothing concrete. I'm not convinced this is a VPASP issue, but thought maybe someone had come across this issue before.
I am not a DB guru and am looking for directions. I've spent considerable time researching and exercising all ideas, but still come back to the same error – it seems to be the connection string to the db – either the version of SQL doesn’t like what VPASP is sending or the OS can’t interpret correctly.
Any help would be appreciated.
Thanks |
|
|
| |
Topic |
|
All Forums
SQL 2005 database issue
New Topic
Printer Friendly
TrustGuard - PCI Security Scanner
