|
Home > Archive > BizTalk Server Applications Integration > June 2004 > BizTalk 2004 configuration wizard
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk 2004 configuration wizard
|
|
| David Collins 2004-06-09, 11:56 pm |
| I have traversed the configuration wizard and have
proceeded as far as the actual configuration process.
However, at the point where the business activity
services messaging and sharepoint site are being
configured, I get the following error:
"A member could not be added to or removed from the local
group because the member does not exist."
Can anyone shed some light on this for me?
Thank You,
David Collins
| |
| Gilles [MSFT] 2004-06-09, 11:56 pm |
| Hello Dave,
>I have traversed the configuration wizard and have
>proceeded as far as the actual configuration process.
>However, at the point where the business activity
>services messaging and sharepoint site are being
>configured, I get the following error:
>"A member could not be added to or removed from the local
>group because the member does not exist."
First, please review the section "Security Requirements" at the following page:
http://msdn.microsoft.com/library/d...config_pwym.asp
If everything is fine there, go to your %temp% directory. There will be a log file called Config(mmddyy hhmmss).log
This log file contains a lot of informations about the configuration process, and the reason for failure as well.
In order for us to better help you, it would be helpful if you could post the relevant parts of this file
(i.e. around the failure point). Also, some knowledge about your configuration (multiple machines/single machine?, OS ...)
would be rgeatly appreciated.
Thanks.
-Gilles.
| |
| beaglez 2004-06-21, 1:08 pm |
| I had the same error come up during the install. I was installing BizTalk 04 developer on an XP Pro machine, with my SQL 2000 sitting on a Win 2000 Server. Finally I realized the problem was I was specifying the domain user in the config wizard as user@DOMAINNAME, and for some reason the Win 2000 Server could not find the user. Once I switched to the DOMAINNAME\user format, I didn't have any problems. Wierd, but true. |
|
|
|
|