owa ya ulaşılamıyor

[Mesut SARIYAR]

Selamlar

2003 Standart Sp2 üzerinde Exchange 2003 sp2, sharepoint service, ftp servis, web servis , sql 2005 çalışıyor.

owa ya ulaşamıyorum,

bozulan owa nın onarılması konulu makaleyi uyguladım ancak değişim olmadı,

Event id yi baz alarak System Managerda bir kaç değişiklilk yaptım ; Topology ' 0 da idi orta düşük ve maximum denedim ama olmadı

event a uyarı olarak Event id: 1040 Source: MSExchangeMU düşüyor

explorerdan açmaya çalıştığımda kullanıcı bilgilerini giriyorum ama "Aradığınız sayfa kaldırılmış, adı değişmiş veya geçici bir süre için kullanılamıyor olabilir." mesajını alıyorum.

sp2 yi yeniden kurdum yine olmadı, sonra domainprep ve tekrar sp2 kurdum yine olmadı..

yardımcı olabilir misiniz

[emreaydin]

Merhaba,

Exchange uzerinde logging i Maximum duzeye getirip bu sekilde bir sure calistirdiktan sonra event log u incelemek cozume bir adim yaklastiracaktir. Ayrica Exchange BPA tool u exchange uzerinde calistirabilir miyiz?

Emre AYDIN

[Mesut SARIYAR]

Maximum düzeyden sonra görülen eventlar bunlardır, maxiumumdan öncede bunlardı..



BPA yı denemiştim daha önce aslında ama fayda etmedi.

[emreaydin]

Merhaba Mesut Bey,

You receive an error when you try to expand the public store folder by using Exchange System Manager in Exchange 2003
http://support.microsoft.com/kb/839744

HOW TO: Configure Recipient Policies in Exchange
http://support.microsoft.com/kb/249299

Birde şöyle bir çözüm mevcut:

- Backup the Metabase
- Stop the Msexchangesa
- Using Metaedit delete the DS2MB key
- Using Metaedit delete the SMTPSVC/1/domain key
- Restart the Msexchangesa

Gelismeleri yazarsanız burdan devam edelim.

Emre AYDIN

[Mesut SARIYAR]

Üstat merhaba,

bu makalelerde bir işe yaramadı malesef, son belirtilen çözümü daha önce uygulamıştım ama bir farklılıkla;

"Using Metaedit delete the SMTPSVC/1/domain key"

ben burada domain key i değil SMTPSVC yi silmiştim, bunun ne tür bir zararı olabilir siz göre?

Sorun bu makalede belirtilen nedenlerdende olabilir http://support.microsoft.com/kb/823265
ama bir sorun var, makalede adı geçen SharePoint Yönetim Merkezi de çalışmıyor, yukarıdaki resimde bununla ilgili bir event vardı, event id den yola çıkarak bir kaç işlem yaptım ama yemedi malesef... çok "kıl" bir durum

[emreaydin]

Mesut Bey Merhaba,

Asagidaki gibi bir hotfix var

FIX: You receive a "The page cannot be found" error message when you click the URLs of certain items that are returned in the search results in SharePoint Portal Server 2003
http://support.microsoft.com/kb/835708

SYMPTOMS
If you configure Microsoft Office SharePoint Portal Server 2003 to crawl and index the public folder store of a computer that is running Microsoft Exchange Server 2003, you may not be able to access certain items that are returned in the search results after you search for content in the public folder store. When you click a URL that is listed in the search results, you receive the following error message:
The page cannot be found.

HTTP 400 - Bad Request
Back to the top

CAUSE
This problem may occur if Microsoft Outlook Web Access (OWA) items that contain one or more angle brackets (< or &gt in the subject line are returned in the search results. SharePoint Portal Server 2003 incorrectly encodes the < and > characters that are contained in the URLs of OWA items that are returned in the search results.
Back to the top

RESOLUTION
This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest SharePoint Portal Server 2003 service pack, you do not have to install the hotfix.
Back to the top

Service pack information
This problem is corrected in SharePoint Portal Server 2003 Service Pack 1.

To resolve this problem, obtain the latest service pack for Microsoft SharePoint Portal Server 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
889380 (http://support.microsoft.com/kb/889380/) How to obtain the latest service pack for SharePoint Portal Server 2003
Back to the top

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SharePoint Portal Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
----------------------------------------------------------------------------
30-Jan-2004 04:20 11.0.5716.1 4,602,616 Microsoft.SharePoint.Portal.dll

Note This update requires SharePoint Portal Server 2003. You may have to restart your computer after you apply this update.
Back to the top

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
This problem was first corrected in SharePoint Portal Server 2003 Service Pack 1.

[Mesut SARIYAR]

Emre Bey, belirtilen hotfix sharepoint service 2.0 service pack2 içerisinde varmış ve sp2 kurdum ama yine yemedi malesef.

sharepoint yönetim merkezi ni açabilseydik sanırım owa yı kurtarabilecektik.

aklınıza başka bir yöntem gelirse yazın lütfen.

ilginiç için teşekkürler.

[emreaydin]

Mesut Selamlar tekrar,

Biraz arastirdim ama asagidaki gibi bir cozum var ne kadar cozum olur orasi tartisilir gerci,

http://support.microsoft.com/default...b;en-us;312422

SYMPTOMS
When you try to log on to Outlook Web Access through an Exchange 2000 front-end server in a "front-end and back-end" cluster topology, you may receive the following error message:
HTTP 404: Page Cannot be Found
However, you can successfully log on to Outlook Web Access if you bypass the front-end server by logging on to Outlook Web Access through an Exchange 2000 Server that serves as a back-end server in the cluster.
Back to the top

RESOLUTION
To let users to log on to Outlook Web Access through the front-end server, use either of the following methods.
Back to the top

Remove the host header NetBIOS name
If your default Web site is shut down, edit the existing virtual server entry, and then delete the entry in the Host Name box so that it is blank. To do this, follow these steps: 1. Start Exchange System Manager.
2. Expand Servers, click the appropriate server name, expand Protocols, and then click HTTP.
3. Right-click Exchange Virtual Server, and then click Properties.
4. Click Advanced (located to the right of the IP Address menu), and then click Edit.
5. Clear the Host Header Value, and then click OK three times.
6. Quit Exchange System Manager.
For example, in a scenario where the NetBIOS name of the Exchange virtual server is BACK_END_SERVER and the Exchange virtual IP address is 192.168.0.1, the original entry would look similar to the following:
IP Address: 192.168.0.1
TCP Port: 80
SSL Port:
Host name: BACK_END_SERVER


In this example, the existing Host name BACK_END_SERVER would be cleared.


Back to the top

Add Host Headers on your back-end servers
1. Start Exchange System Manager.
2. Expand Servers, click the appropriate server name, expand Protocols, and then click HTTP.
3. Right-click Exchange Virtual Server, and then click Properties.
4. Click Advanced (located to the right of the IP Address menu), and then click Add.

Do not remove the existing host header name, for example, the Exchange Server computer virtual net name. Exchange Server Cluster Services requires a specific virtual server name in the Host Header field.
5. Add the following host headers. (The IP address is still the same; only the host header name changes.)• The NetBIOS name of each front-end server.
• The NetBIOS name of the cluster resource.
• The IP address of each front-end server.
• The fully qualified domain name (FQDN) of the front-end server or servers.
• The IP address of the back-end server.
• The NetBIOS name of the back-end server.

6. For fault tolerance, make the same changes on the second node of the cluster.

If you are using Windows Load Balancing, you also have to add a host header for the virtual IP address of the Windows Load Balancing resource. Additionally, it may be useful to add host headers to your front-end servers.

Ayrica,

Exchange setup ini -repair paramatresi ile calistirip owa yi ayaga kaldirmayi deneyebiliriz.

Emre.

[Mesut SARIYAR]

Merhaba tekrar,

belirtilen yollar exchange 2003 kullandığımdan olsa gerek bende mevcut değil (4.adım Advanced)

repair yaptım ama yine olmadı, bence sorun yukarıda verdiğim sharepoint makalesindeki ayarlarda saklı ama sharepoint yönetim merkezinid eçmayı başaramadık malesef henüz..

[Mesut SARIYAR]

Merhaba arkadaşlar,

bu konuyu halen çözemedim, buradan bir ders çıkarmak gerekiyor, eğer exchange ve sharepoint bir arada ise "aman dikkat !"

Sağlıcakla.