I didn't get a response for a while, so I asked this question again in a
different post - and got an answer that worked (for me).
The "solution" was to re-name the SQL instance from "MSSQLSERVER" to
"MSSMLBIZ." BCM seemed to like that better, and it worked. (For me at least -
your milage may vary.)
"Phil" wrote:
[Quoted Text] > Instead of using SERVERNAME\MSSQLSERVER,1433 use
>
> .\MSSQLSERVER,1433
>
> "Dan k" wrote:
>
> > I have the same problem currently - fixed it with a reinstall of office
> > ultimate but then couldn't set up accounting with multiple users - fixed that
> > problem but now cant re-install bcm....can't win
> >
> > "ksurvell" wrote:
> >
> > > I've got BCM 2007 configured to use my SQL server (installed on a server) as
> > > its database. Each of the workstations can connect properly. I'm even using
> > > the new setup wizard for BCM 2007 that helps with this - it works great.
> > >
> > > However - I needed to install BCM on the server itself - but after BCM is
> > > installed, and during the initial setup (when you choose "Advanced" and give
> > > it the name of your SQL instance & port number; i.e.
> > > SERVER\MSSQLSERVER,1433), it says it can't connect to the server (after about
> > > a 15 second timeout).
> > >
> > > I can't figure it out - it's the Administrator account; and remote users on
> > > other workstations using the exact same settings can connect. Am I missing
> > > something painfully obvious here?
|