Office Communications Server 2007 Front End services fail to start : Microsoft, Office Communications Server 2007, Office Comm Server installed on same win2k3 server as exch 2007

May 17, 2008 01:30am pdt

1. arnold 7,400
2. KCTS 5,600
3. Sembee 5,375
4. Merete 4,500
5. lnkevin 4,100
5. ChiefIT 4,100
7. RobWill 4,000
7. Richard_... 4,000
9. TechSoEasy 3,250
10. honmapog 3,000
11. war1 2,800
12. kieran_b 2,750
13. mass2612 2,500
14. tnpcman 2,000
14. xentelwo... 2,000
14. ThrainSo... 2,000
14. uart 2,000
14. Craig27 2,000
14. avitygrai 2,000
14. duncan_roe 2,000
14. wylie_uk 2,000
14. jwaldon 2,000
14. dnudelman 2,000
14. consultkhan 2,000
14. QBRad 2,000
14. Burns2007 2,000
14. DrKernel 2,000
14. DMTechGr... 2,000
14. weareit 2,000
14. manu4u 2,000
14. robocat 2,000
14. asawatzki 2,000
14. czcdct 2,000
14. ocon827679 2,000
14. huntersvcs 2,000
14. routinet 2,000
14. HonorGod 2,000
14. matrixnz 2,000
14. oBdA 2,000
14. mattaob 2,000
14. alextoft 2,000
14. cohenphil 2,000
14. tswaney 2,000
14. debuggerau 2,000
14. ibrennan 2,000
14. thegordo 2,000
14. MichaelVH 2,000
14. LordOfPorts 2,000
14. c_ross 2,000
14. julianop... 2,000
14. Syngin9 2,000
14. CorpComp 2,000
14. zephyr_hex 2,000
14. SteveShe... 2,000
14. BLipman 2,000
14. mattee76 2,000

1. KCTS 12,600
2. Sembee 12,525
3. MrHusy 9,500
4. mass2612 8,500
5. arnold 8,150
6. ATIG 6,750
7. leew 6,500
7. Merete 6,500
9. ChiefIT 5,600
10. RobWill 4,500
10. Jay_Jay70 4,500
12. StuFox100 4,300
13. lnkevin 4,100
14. Netman66 4,000
14. 65td 4,000
14. Richard_... 4,000
14. zephyr_hex 4,000

04.16.2008 at 11:53AM PDT, ID: 23328383

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.3

Office Communications Server 2007 Front End services fail to start

Zones: Server Software, Server, MS Live Communications Server

Tags: Microsoft, Office Communications Server 2007, Office Comm Server installed on same win2k3 server as exch 2007

We are setting up an HP DL380G5, win2k3x64 with the following. Exchange 2007 is up and running fine. When installing OCS 2007 all the services will start except front end services. We created our own CA to generate the certificates, and everything seemed to work fine with them. The errors in eventlog are as follows in order. I need to know how to resolve this issue and get the services up and running.

Event Type:      Error
Event Source:      OCS Protocol Stack
Event Category:      (1001)
Event ID:      14346
Date:            4/16/2008
Time:            11:00:10 AM
User:            N/A
Computer:      PSBMAIL
Description:
Unable to bind for socket.

Transport:TLS, IP address:192.168.204.8, Port:5061. Error:0x8007271D (An attempt was made to access a socket in a way forbidden by its access permissions.).
Cause: This can occur due to a configuration error or because another program is using the specified port.
Resolution:
Ensure that no other program is listening to the specified port and that the IP address is valid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      OCS Protocol Stack
Event Category:      (1001)
Event ID:      14336
Date:            4/16/2008
Time:            11:00:10 AM
User:            N/A
Computer:      PSBMAIL
Description:
A configured transport has failed to start.

Transport TLS has failed to start on local IP address 192.168.204.8 at port 5061.
Cause: This can occur due to a configuration error, low system resources or other programs using the specified port. It can also happen if the IP address specified has become invalid.
Resolution:
Ensure that the IP address specified is valid and that no other program is listening on the specified port.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      OCS Protocol Stack
Event Category:      (1001)
Event ID:      14352
Date:            4/16/2008
Time:            11:00:10 AM
User:            N/A
Computer:      PSBMAIL
Description:
Unable to start the stack.

Error: 0x0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type:      Error
Event Source:      OCS Server
Event Category:      (1000)
Event ID:      12326
Date:            4/16/2008
Time:            11:00:10 AM
User:            N/A
Computer:      PSBMAIL
Description:
Failed starting the protocol stack. The service has to stop

Error code is:0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED).
Cause: Check the previous entries in the event log for the failure reason.
Resolution:
Try restarting the server after resolving the failures listed in the previous event log entries.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type:      Error
Event Source:      OCS Snap-in
Event Category:      (1004)
Event ID:      30710
Date:            4/16/2008
Time:            11:00:12 AM
User:            N/A
Computer:      PSBMAIL
Description:
Office Communications Server Snap-in failed to start service:
Service Name = RTCSRV

HRESULT = 0x8007042A
Error Description = The service has returned a service-specific error code.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Start your free trial to view this solution

Question Stats

Zone: Software

Question Asked By: silkfire

Solution Provided By: ThrainSonOfTimor

Participating Experts: 1

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

04.16.2008 at 03:00PM PDT, ID: 21372424

ThrainSonOfTimor:

It is a big risk to setup Exchange 2007 and OCS 2007 on the same server.
Exchange UM role and OCS use the same ports which is the problem in your case (port 5061 is shared).
Look here for ports of Exchange 2007: http://technet.microsoft.com/en-us/library/aa998265(EXCHG.80).aspx
Ports of OCS: http://technet.microsoft.com/en-us/library/bb870402.aspx

I recommend to use another server for OCS. If you really need to set it up on one server, you will need to change the ports manually. You have to configure the Remote Access port on the external interface to a port other than port 5061. However if you want to use federation you have to use port 5061 on the external interface.

04.16.2008 at 04:42PM PDT, ID: 21372958

silkfire:

I called MS and they said it cannot be done. So I changed port 5061 to 5086, and at that point OCS would run all services, but it would not pull the user objects from Active directory at that point or give the option to enable OCS for them. It is only a 50 user environment, so there shouldn't be load problems with the server we have it on, but the port issue is apparently going to cause some issues and I can't see a way to import users without it adding them through AD. At this point the client finally just decided to put a small box in for just the OCS server so we are going that direction, but I still think there really shouldn't be a reason not to run all the communications apps on one box, I feel that is MS underdevelopment and not making integration easily attainable. I guess it is more for the fact that Exchange and OCS are truly developed for Enterprise and they really didn't plan on SMB's using them and wanting to keep hardware limited. Virtualization would work I guess, but by the time we get that done putting in a cheap $900 server is just as easy and probably faster in the short term.

04.17.2008 at 12:56AM PDT, ID: 21375007

ThrainSonOfTimor:

Hi silkfire,

Yes, exchange 2007 and ocs 2007 is definitely for the enterprise. There is a new small business server 2008 with exchange 2007 but no OCS. http://www.microsoft.com/windowsserver/essential/sbs/editions.mspx

The reason why you can't add users is because you install a 32bit ocs on a 64bit OS for Exchange. You need to run dsa in 32 bit mode: dsa.msc -32
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2686889&SiteID=17
Or use a 32bit client OS and add active directory users and computers in the msc console.

Virtualization of the exchange 2007 UM role is not supported by microsoft (it is possible though) and OCS is also not supported in virtualisation (http://www.microsoft.com/downloads/details.aspx?familyid=F8CC9B59-225F-425D-BD3A-E506396C6207&displaylang=en, page 11). So you are right, there is still a lot of work to make these products easier for small business. So the 900$ server and a 32 bit OS for the OCS is the fastest and easier way.

Accepted Solution

04.17.2008 at 09:06AM PDT, ID: 21378615

silkfire:

Thank you Thrain, your second answer would have let it work from the exchange server, if I had realized that for some screwy reason the OCS enabling features in AD are not shown by default in x64 DSA.MSC. So in all reality, it was working colocated with the exchange server after the port change from 5061 to 5086, which makes me feel better knowing that I did have it fixed. I guess there is something to be said about taking a bit of a break in the middle of everything (this was only one of the 4 server loads I was doing through the course of two 40 hour weekends). The AD recovery from crash of the only DC, exchange recovery, and rebuild of basically everything worked out, this one was just the final challenge. In 18 years that is my 3rd call to MS, with them refunding my money everytime.

ThrainSonOfTimor

04.17.2008 at 02:43PM PDT, ID: 21381657

Hi Silkfire,

Glad you sorted it out, but whow that are hell of weekends. And yes, it would work with the port change in my opinion. And for your information: OCS and Exchange 2007 in virtualisation is running fine in my test environment, but supported from microsoft on best effort in production.

With kind regards,

Jef

20080236-EE-VQP-29 / EE_QW_2_20070628