|
|
|
date: Mon, 23 Jun 2008 13:42:04 -0700,
group: microsoft.public.cmserver.general
back
Network changes hosed my development environment
Hi everyone,
While I was out on vacation last week, the network guys made some changes to
the network. Previously we were on Network #1, we split that network and
domain and are now on Network #2. My network login was previously
network1\jgrimmer, now it is network2\jgrimmer. During all the fun network
changes that happened last week, my workstation's name was changed from
worknet-6978796 to grimmer-j. As you can imagine, my MCMS install was set to
use a database on worknet-6978796. The database is now on grimmer-j.
If I try to go into Site Manager, I get the following message when trying to
connect to localhost (grimmer-j):
"The list of domains is not available due to the following error: Extended
error: [What='IAESession3::GetConfiguredDirectories: SQL Server does not
exist or access denied. ConnectionOpen (Connect()). Invalid connection
string
attribute.'][LCID='1024][SourceFile=''][SourceFileLine='-1'][DebugInfo=''][RecommendedAction='The
ODBC data source may be incorrectly configured, the database may not be
running, or there may be incorrect data in the
database.'][ExtraInfo=''][UniqueErrorId='4005'][Severity='5'][Source=''][CategoryId='0']"
If I click "OK" I get the "Logon as jgrimmer or Logon as the following user"
options. If I try to logon as jgrimmer (which is probably admittedly a bad
idea because jgrimmer is now associated with domain network2 instead of
network1) I get "SQL Server does not exist or access denied.
ConnectionOpen(Connect()). Invalid connection string attribute." If I try
to logon using the other option (I have a local "jgrimmer" user set up that
existed before the network split), and try to login with the local ID, I get
the same error message.
By now I've figured out that this is a SQL problem, so I fire up SSMS, and
make sure that the database I'm using (VOS_MCMS_Edit) has a user that is a
DBO (network2\jgrimmer) and fire up the MCMS DCA. I can get to the screen
where I can select a database. It shows the old location of my database,
worknet-6978796.VOS_MCMS_Edit. When I hit the "Select Database" button to
put in the new database location, GRIMMER-J.VOS_MCMS_Edit, I get the SQL
login dialog. Here's another spot I am having problems. I change my server
from the old name, worknet-6978796, to the new name, grimmer-j. I leave the
"Use Trusted Connection" box checked, and get the following message: "Using a
SQL Login to access the database requires that this Login have DBO rights
because it is used by this application to configure the database. Using
Trusted Authentication to access the database only requires that the
previously defined MCMS system account have the following database
privileges: db_datareader, db_datawriter, and db_ddladmin." Now
network2\jgrimmer does have DBO rights to the database I want to use. It
also has the db_datareader, db_datawriter, and db_ddladmin rights. I've also
tried it using a sql login with dbo rights, and I get the same error message.
Sorry for the long-winded post, but how do I fix this?
jgrimmer
date: Mon, 23 Jun 2008 13:42:04 -0700
author: jgrimmer
Re: Network changes hosed my development environment
Hi Chandy,
the names of the IUSR and IWAM accounts are not relevant.
Many customers replace them with domain accounts to have the same name on
different machines.
So that is not a reason not to rename a machine.
Cheers,
Stefan
"Chandy" wrote in message
news:3ff3effd-e157-4b27-bcbb-dd6a096b8d22@25g2000hsx.googlegroups.com...
> On 23 Jun, 21:44, jgrimmer wrote:
>> I should also mention that we're on MCMS 2002 SP2 on WinXP Professional
>> for
>> our Development environment.
>>
>> jgrimmer
>
> Hi,
>
> In my experience, it is a very bad idea to re-name a Windows machine,
> and many applications and services can suffer from the process. As a
> start, your IUSR_ and IWAM_ accounts will likely now have the 'wrong'
> names.
>
> If I were you, I would completely flatten and re-install your
> development environment as it would likely be a quicker fix in the
> long-run.
>
> Chandy
date: Fri, 4 Jul 2008 08:29:03 +0200
author: Stefan Goßner [MSFT]
|
|
