error=49153 2

[MrTreehorn]

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?

 

[Jay Converse]

49153 means the SQL server you're referencing isn't running, or isn't accepting remote connections.

 

[MrTreehorn]

So all the other workstations are running fine. I have looked and tested many times but I must have a problem in the ODBC settings. Is this the right direction to look.

Perhaps this "computer" is not authorzed to accept remote connections.

 

[ettienne]

There are no compatibility issues, I'm running 5.6 and SQL 2005 on Win 7 and it's just fine. As Tuba said, check the SQL server remote connections and turn of the firewall on the server.
BTW why are you creating ODBC DSNs? If done right then this is not necessary on a workstation, unless you are running a 64bit OS.

 

[Jay Converse]

Or Windows Firewall is running.
Or the DNS is wrong, and the server name isn't resolving.

 

[MrTreehorn]

Turning off the windows firewall didnt work.

I may be getting outside of my paygrade here but thats how my Accpac Provider taught me to do my workstation install.

First I run \\servername\ACCPAC56\WSSetup\setup.exe
set the program and data directories.

Second I go to Data Sources (ODBC) and under System DSN tab click Add_SQL Navive Client and setup using my servername and server user\pass. Test connection.

Are you saying the System DSN step is not required?

 

[MrTreehorn]

I now see that the system I bought is setup as 64-bit. Im assuming this may be a factor.

 

[DjangMan]

Start, Run, %WinDir%\syswow64\odbcad32.exe

 

[MrTreehorn]

That did it. Thanks. Great forum. Quick!!!

 

[ettienne]

In Accpac database setup I always use the server name instead of an ODBC datasource name (the bad way of setting it up), that way you do not have to manually create ODBC DSNs on each 32 bit workstation - except for 64 bit workstations. With 64 bit workstations you need to run the 32bit ODBC admin and create the DSN, and remember to delete the 64bit DSN.

 

[Yorkshireman2]

To Djangman,

I just installed Accpac on a Windows 7 64-bit pc and we get error 49153 saying there is a DSN architecture mismatch between the Driver and application.

I tried Start, Run, %WinDir%\syswow64\odbcad32.exe as you said But it only brings up the ODBC properties/setup window- is the command supposed to fix the problem?





Yorkshireman2

 

[ettienne]

You are supposed to fix the problem in the ODBC administrator that pops up. You need to create and System DSN for the SSQL Native Client and use the server name + 32 for the DSN name, i.e. if your server name is server then the DSN name will be server32.

 

[Yorkshireman2]

Thanks ettiene,
I'll try this tomorrow.
Chris

Yorkshireman2

 

[Yorkshireman2]

ettiene,
Thanks- got Accpac opening ok like that.
The last problem is that this one user gets a crash in the Technisoft Service Manager add-in when she clicks 'View Custom Fields' in v/m document entry-> new document.

But Accpac does run in Windows 7 64 bit now- thanks.


Yorkshireman2

 

[DjangMan]

You might try turning off DEP for the VM executables. Service Manager screens are all separate .exe files whereas Accpac screens are .ocx files (activeX controls).

Technisoft support might have a solution as well.

 

[Yorkshireman2]

I emailed Technisoft - no reply yet.
This is odd... We gave this lady a new Accpac user id to try and she now finds that the View custom fields button works properly- no crashing. (Note that her old login began to cause the same problem on her old XP computer as well after using the login on the Windows 7 PC.

BUT.. now whenever she tries to use Accounts Payable, receivable etc. it tries to run an install process and fails, saying that an ocx control is not registered properly.


Yorkshireman2

 

[ettienne]

Login on that computer with administrator rights and then right-click on REGACC.EXE (found in the \Accpac\Runtime folder) and Run As Administrator.

 

[Yorkshireman2]

Oh- forgot to add.. the installer fails with th is type of error:
Copy Error" An error occurred while copying fiel (1)ACCPACPO1210.OCX.
Cannot copy file to destination directory".

The details that came up were:
*** Code Download Log entry (23 Apr 2010 @ 11:49:45) ***
Code Download Error: (hr = 80040154) Class not registered

Operation failed. Detailed Information:
CodeBase: C:\PROGRAM FILES (X86)\ACCPAC\PO53B\ACCPACPO1210.OCX
CLSID: {7D0E9463-D0F4-4A3D-AEEB-58FE1D9D20ED}
Extension:
Type:

LOG: Setup successful installing: ACCPACPO1210.OCX to (null) destination code(0)
--- Detailed Error Log Follows ---
LOG: Download OnStopBinding called (hrStatus = 0 / hrResponseHdr = 0).
LOG: URL Download Complete: hrStatus:0, hrOSB:0, hrResponseHdr:0, URLfile:///C:/PROGRAM%20FILES%20(X86)/ACCPAC/PO53B/ACCPACPO1210.OCX)
LOG: Setup successful installing: ACCPACPO1210.OCX to (null) destination code(0)
LOG: Version not identified for , using 0.1.
LOG: Reporting Code Download Completion: (hr:80040154, CLASSID: 7d0e9463..., szCODEC:\PROGRAM FILES (X86)\ACCPAC\PO53B\ACCPACPO1210.OCX), MainTypenull), MainExtnull))

-----------

This used to happen last Thursday then it stopped (not sure what I fixed) but the crash from 'View Custom fields' problem remained.
Now the crash problem is fixed with a new login, this other problem is back!
The fact that her old login used to work in XP but now has the same problem after using Windows 7, seems to suggest that the Windows 7 has corrupted her user account profile or something?
Therefore the new login account allows her to use Service Manager without the Custom fields crash, but she can't use anything else in Accpac now.


Yorkshireman2

 

[Jay Converse]

Rule #1 of Vista and Windows 7 is not to install to the default Programs folder.

Rule #2 is that you shouldn't be doing location program installs, but that's another argument.

 

[DjangMan]

Follow rule #1 (and #2) but in this case #1 is very important.