SQL Conflict with ACT 2006

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a computer with Microsoft Office Professional installed, plus
Microsoft Small Business Accounting. When I try to install ACT 2006, it
generates a login failure error 1069 message.

ACT ( Sage ) says this is a defect in the Microsoft SQL Server technology
and that the programs cannot co-exist. They specifically blame it on Small
Business Contact Manager.

I can't say that this makes sense to me because I would think it would
create a separate instance for each program, which does show in the running
services, but even though there is an ACT 7 service running, the login fails.


They can offer no support beyond blaming Microsoft and saying that a fix is
on the way from Microsoft.

Cany anyone shed some light on this, and is there a technical bulletin that
sheds a light on this ? I could not find anything in a search of the
Knowledge Base.

Thanks and have a wonderful day !

Tim
 
First time I've heard about this. SBA and BCM use the same sql instance
and I'm not aware of them having tweaked sql in any way.

However, they do create their own sql instance, and then turn off a
bunch of features they don't use, like the udp port. This is a
recommended security practice these days. This instance may be
confusing ACT's Setup program. It detects SQL is already installed, and
doesn't install its own instance, but then ACT can't communicate to the
instance because the typical UDP port redirector service doesn't
respond.

I'm just guessing here.

But, you could try installing a default/generic sql server instance,
and then rerunning the ACT install.
 
ACT does install, and start, MSSQL$ACT7 as a service. However when the
program tries to login to an existing database, or to create a new one, it
fails with an error 1069:

"A service operation failed for the MSSQL$ACT7 service: 1069 The service did
not start due to a logon failure."
 
Back
Top