Community
Showing results for 
Search instead for 
Do you mean 
Reply

***Problem after 2010 Update***

Accepted Solution Solved
Copper Elite Contributor
Posts: 148
Country: United States
Accepted Solution

***Problem after 2010 Update***

I am receiveing this error

Sqlcmd: Error: Connection failure. SQL Native Client is not installed correctly. To correct this, run SQL Server Setup.

I updated 2010 Prem to the newest update today 3/9/10 and getting this error when it is trying to convert the RDB to the newer version. Any ideas? Thx.


Accepted Solutions
Solution
Accepted by topic author briannydish
‎09-25-2015 03:20 AM
Platinum Elite Contributor
Posts: 6,537
Country: USA

Re: ***Problem after 2010 Update***

If you open ACT! Diagnostics, can you verify that the remote database is connected to SQL? Also, a couple of things you can try:

 

- Go to your Services (type in "services.msc" in the Run (XP) or Search (Vista/7) box in your Start menu) and stop/restart the SQL Server (ACT7) service

- Browse to C:\Program Files\ACT\Act for Windows, locate the file SecurityCmdLnApp.exe, and double-click to run

Greig Hollister

Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.

View solution in original post


All Replies
Solution
Accepted by topic author briannydish
‎09-25-2015 03:20 AM
Platinum Elite Contributor
Posts: 6,537
Country: USA

Re: ***Problem after 2010 Update***

If you open ACT! Diagnostics, can you verify that the remote database is connected to SQL? Also, a couple of things you can try:

 

- Go to your Services (type in "services.msc" in the Run (XP) or Search (Vista/7) box in your Start menu) and stop/restart the SQL Server (ACT7) service

- Browse to C:\Program Files\ACT\Act for Windows, locate the file SecurityCmdLnApp.exe, and double-click to run

Greig Hollister

Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.

Employee
Posts: 18
Country: USA

Re: ***Problem after 2010 Update***

This resolved our issue thank you Greg.