خطا در ایجاد بانک اطلاعاتی هنگام نصب OCS

سلام
من موقع نصب OCS 2007 Enterprise Edition به این خطا برخورد میکنم.
در قسمت Create Enterprise Pool
[CODE]
Unable to get back the configuration database version . .
[/CODE]
کسی میتونه راهنمایی کنه ؟

install service pack sql server

Sql 2005 With Service Pack 3
Sql 2000 With Service Pack 4
اما هیچ کدام جواب نداد

نسخه SQL Enterprise رو نصب و به آخرین سرویس پک ارتقا بدهید.
چک کنید که SQL وقتی اجرا میشه بدون خطا باشه .

منظور شما چیه ؟
من Sql 2000 و 2005 نسخه Enterprise نصب کردم همراه آخرین Service Pack
اما نشد.
Sql اجرا مشیه بدون مشکل.

اساتید اهل فن، تا بحال کسی نصب نکرده بخواد به من کمک کنه ؟

یعنی کسی سراغ این نسخه Enterprise یا R2 نرفته ؟

موقعی که Sql Express خود OCS نصب میکنم بدون خطا تا آخر میاد اما آخرین لحظه این خطا میده.
[CODE]
Failure [0xC3EC79FBP]
The edition of SQL Server installed on the back-end computer is not supported for creating an Enterprise pool.
A Standard or Enterprise of SQL Server is required.
[/CODE]

موقعی که Sql Enterprise نصب میکنم مرحله Detecting Pool Backent خطا میده ولی به Continue رد میشه اما آخرین لحظه این خطا میده.
[CODE]
Failure [0xC3EC78C6]
The version of SQL Server installed on the back-end is not supported.
SQL 2000 SP4 or later, or SQL 2005 SP1 or later required.
[/CODE]

و اما موقعی که روی SQL Ent Sp3 نصب میکنم مثل حالت قبل تو مرحله Detecting Pool Backent خطا میده ولی به Continue رد میشه اما آخرین لحظه این خطا میده.
[CODE]
Failure [0xC3EC783E]
Failed to open SQL database.
[/CODE]

[LEFT][CODE]http://www.shudnow.net/2009/06/01/create-pool-run-on-ocs-or-sql-server/[/CODE][B][SIZE=3]Create Pool – Run on OCS or SQL Server?[/SIZE][/B]

The guidance around where to create your pool and why can be quite confusing.
If you look at the OCS R1 requirements for deploying an Enterprise Pool, it tells you the following:

[LIST][*]If you are using a 32-bit version of SQL Server, log on to your Office Communications Server Back-end Database server as a member of the Domain Admins group.[*]If you are using a 64-bit version of SQL Server, create the pool by using a computer with a 32-bit processor, such as the computer that you plan to use as the Front End Server. Log on to the 32-bit processor computer as a member of RTCUniversalServerAdmins and Domain Admins group and with user rights to create and modify SQL Server databases.[/LIST]
If you look at the OCS R2 requirements for deploying an Enterprise Pool, it tells you the following:

[LIST][*]If you are using a 64-bit version of SQL Server, log on to your Office Communications Server Back-end Database as a member of RTCUniversalServerAdmins and DomainAdmins group.[*]If you are using a 32-bit version of SQL Server, create the pool by using the computer that you plan to use as the Front End Server. Log on to this computer as a member of RTCUniversalServerAdmins and Domain Admins group and with user rights to create and modify SQL Server databases.[/LIST]
As you can see, it’s a complete 180 between R1 and R2. To make it easier to digest, here’s an easier format to see what you should do:
OCS R1 with SQL 32-bit – Create Pool on SQL
OCS R1 with SQL 64-bit – Create pool on OCS FE
OCS R2 with SQL 32-bit – Create Pool on OCS FE
OCS R2 with SQL 64-bit – Create Pool on SQL
The reason why it’s a complete 180 is because Microsoft wants you to run the installer on the native platform of the installer. OCS R1 is 32-bit so you always want to run the installer on a 32-bit machine. OCS R2 is 64-bit so you always want to run the installer on a 64-bit machine.
But the million dollar question is, is it really necessary to run it from the Backend? Does that mean you have to insert your OCS CD, install .Net Framework, Visual C++, etc…. Well, you could, but you can use LCSCMD to configure your pool instead. LCSCMD is on your CD and you can just open a cmd prompt, navigate to your cd-rom, and run the LCSCMD command with the appropriate settings to configure your pool without needing to install at the tools the installer GUI would require. LCSCMD would also bypass the requirement from running the installer on the same processor platform (x86/x64.) You can refer to the following article [SIZE=3][B][URL="http://technet.microsoft.com/en-us/library/dd572486%28office.13%29.aspx"]here[/URL][/B][/SIZE] for information on how to use LCSCMD to create an Enterprise Pool.
But, that doesn’t really explain why it is recommended running it on the Backend. After talking with Ken Alverson from Microsoft about this, I learned a few things. The reason they recommend to create the pool on the SQL Server is to minimize the possibility of firewall/permissions from interfering. The Create Pool requires access to both SQL as well as WMI. You can technically open up all the ports to SQL as well as WMI and run Configure Your Pool from your OCS Server. This is what I did but instead of opening it completely, I ran Network Monitor to determine what ports to open. You could also disable your Windows Firewall on your SQL Server to ensure access to your SQL Server. Never disable the firewall service on Server 2008 as this disrupts proper communication. Either turn the firewall off or go into the advanced firewall in the administrative tools and open everything up.
So in short, you have the following options with OCS R2:

[LIST=1][*]Turn off firewall on SQL (don’t disable firewall service) and install from OCS Server (lowers security but easiest to do.) After the pool is created, you can re-enable your firewall as long as you follow the OCS documentation (installation guide for Enterprise Edition) and open the necessary ports.)[*]Allow SQL Ports and WMI to traverse SQL Firewall (more secure than #1 but less easy to do)[*]Run Create Pool from SQL Server via the GUI Installer (more secure than #1 and #2 but not an option I like due to it installing GUI prerequisites)[*]Run Create Pool from LCSCMD via the CD which will install a SQL prerequisite I believe (most secure option but requires knowledge of the LCSCMD command.) You can refer to the following article [SIZE=3][B][URL="http://technet.microsoft.com/en-us/library/dd572486%28office.13%29.aspx"]here[/URL][/B][/SIZE] for information on how to use LCSCMD to create an Enterprise Pool.[/LIST]
I would appreciate if readers can make a quick comment on what method you use
[/LEFT]

[LEFT][CODE]http://www.ocspedia.com/Misc/OCS_2007_Permissions.htm[/CODE][COLOR=Black]
[/COLOR][SIZE=2][COLOR=Black][B][FONT=Verdana]OCS 2007 Permission Requirement [/FONT][/B][/COLOR][/SIZE][COLOR=Black]
[/COLOR]
[COLOR=Blue][B]Create Pool[/B][/COLOR]
Domain Admins, [B]RTCUniversalServerAdmins[/B] and Local Administrator on the back-end

[B][COLOR=Blue]Configure Pool[/COLOR][/B]
[B]RTCUniversalServerAdmins




[/B][B]Office Communications Server 2007 R2 Enterprise Deployment

[/B][CODE]
http://forum.persiannetworks.com/f101/t27599.html
http://forum.persiannetworks.com/f101/t27600.html
[/CODE] [/LEFT]

عزیز ممنون
من همه اینارو دیدم
اما هیچ کدوم جواب سوال من نبود
همه یک چیز نوشتن
اما عکس، متنی نگفته چطور Sql نصب کنم و پیکربندی

آقایون مشکل من حل شد.
موفق باشید.

جناب آقای یوسفی
نوشته "آقایان مشکل من حل شد، موفق باشید" اهانتی است به همه عزیزانی که در این انجمن فعالیت می کنند.

ممنون می شوم اگر راه حلی که پیدا کردید را بنویسید تا دیگران نیز استفاده کنند.

سلام
من قصد اهانت به کسی رو نداشتم
اما مشکل من که تو هیچ جا ذکر نشده بود الا یک انجمن خارجی
باید 3 تا دیتا بیس تو Sql 2005 بسازیم
به نامهای
rtc
rtcconfig
rtcdyn
موقع نصب باید گفته شه که replace بشه.

حالا من دارم ocs روی یک کامپیوتر عضو دامین نصب میکنم که به مشکل خوردم.
فردا error میزارم شاید کسی برخورده باشه.

با سلام
این خطایی که من موقع نصب OCS بر روی یک کامپیوتر عضو دامین میگیرم.
راستی این علامت کد نیست تو این تم.
اینم خطا
[B][COLOR=red][FONT=Tahoma]Failure [0xC3EC78E8] Primary DNS Suffix of this computer is in an inconsistent state[/FONT][/COLOR][/B]
تو اینترنتم اینجا مطرح شده
اما من نفهمیدم منظورشو

[url=http://social.technet.microsoft.com/Forums/en/ocsplanningdeployment/thread/4e7bfcbe-0342-4fe0-aa97-ae20a167cf02]OCS 2007 Primary DNS Suffix Inconsistent state[/url]

کسی به این مشکل برنخورده یا راه حلی نداره ؟

میشه یه خروجی از ipconfig /allاینجا بزارید

مشکل از DNS Server بود.
با نصب مجدد DNS Server مشکل حل شد.