Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

error=49153 2

Status
Not open for further replies.

MrTreehorn

Technical User
Dec 3, 2009
5
CA
I have just installed Accpac 5.6 workstation setup and setup the SQL Native Client in ODBC but now when I run Accpac ERP and put in my USER\PASS I get...

“Cannot access database (error=49153. See help for more information.”

Note: this is a Windows 7 machine. Is there compatibility issues?
 
Just to add to that... run scanisam to see if you have any corrupted user isam files.
 
Hi- please explain- I have always followed a set of install instructions made up a couple of years ago and they say use the defaul install location.

Where should I install it to?



Yorkshireman2
 
Read the installation documentation for Accpac 5.6 - it specifically says do not install to the default folder on Vista/Win7.
Start, Programs, Accpac, Tools, Scanisam
 
Ah- we have Accpac 5.3 so the install instructions probably wouldn't include Windows 7 on them. To be honest I don't know where the install documentation for this one is either- It was all done long before I was asked to look at this.
I only know a set of instructions in a .txt document, made up by our previous IT man (died suddenly last year).


"Rule #2 is that you shouldn't be doing location program installs" please explain what you mean by 'location program installs'.


Yorkshireman2
 
You shouldn't be installing Accpac on each workstation, it's extra work when you need service packs. You put it on a shared network location, then run ..\Wssetup\Setup.Exe on each workstation.
 
Tried scanisam- no errors were described- just a lst of files printed out in the results window.

I have set REGACC.EXE to run as administrator.
Also removed the ODBC connections and re-added them using syswow 64 odbcad32, naming then with a It complained about database specification.
I had to remove the 32 from the name. It seems Accpac expects the proper database name without any 32 added.


Our boss gave this user two new login accounts today and she finds one new account lets her use the View Custom Fields of Service Manager on the Windows 7 PC (but other ACCPAC fetaures trigger the ACCPAC installer and the 'fail to instll' message.
If she runs into the next office, the old login on her XP PC allows her to use the ACCPAC features but no custom fields feature.

We are about to scrap the Windows 7 PC and not allow anybody to upgrade to a new PC ever.
There was no problem with the old XP computer originally.


Yorkshireman2
 
What about running in XP compatibility mode (assuming you have the 'high' enough version of Win7)?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top