MattRichardson
Wed Jul 23 14:45:03 CDT 2008
Adam-
I need to update my blog, but I combed through the database, and changed
everything that mentioned my old server name. There is a GUID in there
somewhere that needs to be reset. The Configuration Manager is the tool that
can do it.
Another thing I ran into, that I wouldn't have if I the rename process steps
were followed, was that when I ran a:
select * from sys.servers
It brought back two instances. I had to delete them both, and create just
Instance 0 as the server name, and then it worked.
Sorry for the two separate posts.
Regards,
-Matt
"AdamEdmonds" wrote:
> Yes, and I did a Repair on the CRM Server, which (I'm assuming) should have
> fixed any permissions issues. I'm able to connect to the databases (using
> the connection strings in the CRM server's registry) via Visual Studio. One
> string uses a SQLOLEDB object and 2 use SQLConnections. All connected fine,
> but still no luck on the CRM Server.
>
> Thanks,
> Adam
>
> "Darren Liu" wrote:
>
> > Hi Adam,
> >
> > Did you start the SQL agent?
> >
> > Darren
> >
> > On Jul 21, 10:08 am, AdamEdmonds
> > <AdamEdmo...@discussions.microsoft.com> wrote:
> > > I've managed to do this once, but all I get now is a generic message:
> > >
> > > An error has occurred while establishing a connection to the server. When
> > > connecting to SQL Server 2005, this failure may be caused by the fact that
> > > under the default settings SQL Server does not allow remote connections.
> > > (provider: Named Pipes Provider, error: 40 - Could not open a connection to
> > > SQL Server)
> > >
> > > Any help is greatly appreciated.
> > > Thanks,
> > > Adam
> >
> >