Archive for June, 2009

Logging thousands of errors, oerflib and sbsmonitoring

Thursday, June 18th, 2009
I’m receiving these two errors again and again:

 

Windows cannot load extensible counter DLL MSSQL$MSFW, the first DWORD in data section is the Windows error code.

 

Windows cannot load extensible counter DLL MSSQL$SBSMONITORING, the first DWORD in data section is the Windows error code.

 

What might be generating them and how can I cure it?

 

The system is SBS 2003 R2 Premium.

 

Thanks.

Answers

  • TrxAdmin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers MedalsThursday, May 10, 2007 1:57 PM

    Answer

    According to the KB article below, it is a permissions issue:

    “To resolve this problem, you must grant the Read & Execute permission to the Network Service account on the performance counter DLL for SQL Server 2005 Analysis Services.

    http://support.microsoft.com/kb/912399

All Replies

  • mrdennyMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers MedalsThursday, May 10, 2007 1:57 AM

    Where are you seeing these errors?
  • TrxAdmin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers MedalsThursday, May 10, 2007 1:46 PM

    I am also getting thousands of these errors in the application log of 3 SBS machines.

    They are all running SBS 2k3 sp1, at least 1 of them is R2 version of 2k3.

  • TrxAdmin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers MedalsThursday, May 10, 2007 1:57 PM

    Answer

    According to the KB article below, it is a permissions issue:

    “To resolve this problem, you must grant the Read & Execute permission to the Network Service account on the performance counter DLL for SQL Server 2005 Analysis Services.

    http://support.microsoft.com/kb/912399

  • Old Blind Dog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers MedalsFriday, May 11, 2007 11:56 AM

    The 912399 article says:

    RESOLUTION

    To resolve this problem, you must grant the Read & Execute permission to the Network Service account on the performance counter DLL for SQL Server 2005 Analysis Services. The DLL is located in the following folder:

    C:\Program Files\Microsoft SQL Server\MSSQL.x\OLAP\Bin\Msmdctr90.dll

    Additionally, you must grant Read permissions to the Network Service account on the “bin” directory and the “bin\en” directory for SQL Server 2005 Analysis Services. For example:

    C:\Program Files\Microsoft SQL Server\MSSQL.x\OLAP\bin
    C:\Program Files\Microsoft SQL Server\MSSQL.x\OLAP\bin\en

     

    I didn’t have those specific directories, but I gave Network Service permissions for any similarly named directories and it fixed the problem. Thanks

    Any idea what created the problem to begin with?

  • Anonymousbhnmkjh Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers MedalsMonday, May 14, 2007 11:04 AM

    I have this problem for an earlier MSSQL server version which does not have the same structure.  does anyone know the method for this?

     

     

Need Help with Forums? (FAQ)

Statistics

  • Started: 5/4/2007
  • Last Reply: 5/11/2007
  • Helpful Votes: 0
  • Replies: 5
  • Views: 2,660

How to redirect an HTTP connection to HTTPS for Outlook Web Access clients and how to redirect the Default Web Site to point to the Exchange virtual directory

Wednesday, June 17th, 2009

This is a Microsoft solution! - Official Link: http://support.microsoft.com/kb/839357

This article describes how to automatically redirect an HTTP connection to an HTTPS connection in the Internet Information Services console (IIS) for Microsoft Office Outlook Web Access (OWA) users. This article also describes how to modify the IIS Default Web Site so that clients can access the Outlook Web Access logon page by typing only http://<server name> instead of typing http://<server name>/exchange.

We recommend that you require a Secure Sockets Layer (SSL) connection for your OWA users. An SSL connection encrypts the information that is sent to or received from the Microsoft Exchange Server computer. However, when you configure IIS to require SSL for all incoming OWA requests, OWA users who try to connect by using HTTP receive the following error message:

HTTP 403.4 - Forbidden:
SSL required
Internet Information Services

After the OWA user receives the error message, the user must manually type https:// at the start of the URL to connect to the Exchange Server computer. You may want to configure IIS to automatically redirect the OWA user’s HTTP request to HTTPS to minimize user interaction and to make sure that all incoming requests are enabled for SSL.

MORE INFORMATION

To configure IIS to automatically redirect HTTP requests as HTTPS requests, foll…

To configure IIS to automatically redirect HTTP requests as HTTPS requests, follow these steps.

Important If the following conditions are true, you must mount and start the mailbox store before you can successfully complete these steps:

  • Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 is installed on a front-end server.
  • The mailbox store has been dismounted.

Note Follow these steps on an Exchange front-end server that communicates with a clustered Exchange back-end server.

  1. Create an Active Server Pages (ASP) Web page that contains the following code:

     <%
    
    If Request.ServerVariables("HTTPS")  = "off" Then
    						Response.Redirect "https://" & Request.ServerVariables("HTTP_HOST") & "/Exchange"
    End If 
    
    	%>

  2. Name the Web page “Owahttps.asp.”
  3. In Windows Explorer, create the Inetpub\Wwwroot\CustomErrors folder, and then save the Owahttps.asp Web page file to that folder.
  4. Start the IIS console.
    • In Windows NT Server 4.0 (IIS 4.0)

      Note Follow these steps if you are running Microsoft Exchange Server 5.5 OWA on Windows NT 4.0 Server together with the Windows NT 4.0 Option Pack. If you have an Exchange Server 5.5 mailbox server, and if the OWA component is installed separately on a dedicated Web server, follow these steps on the Web server only.

      1. Click Start, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information Services, and then click Internet Services Manager.
      2. Expand Internet Information Server, expand Computer Name, and then expand the Web site that the OWA users use to access their Exchange server. By default, this Web site will be the Default Web Site.
      3. Go to step 5.
    • In Windows 2000 Server (IIS 5.0)

      Note Follow these steps if you are running Exchange Server 5.5, Exchange 2000, or Exchange 2003 OWA on Windows 2000 Server.

      1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
      2. Double-click Computer Name to expand the computer object.
      3. Expand the Web site that the OWA users use to access their Exchange server. By default, this Web site will be the Default Web Site.
      4. Go to step 5.
    • In Windows Server 2003 (IIS 6.0)

      Note Follow these steps if you are running Exchange 2003 OWA on Windows Server 2003.

      1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
      2. Expand Computer Name, and then expand Web Sites.
      3. Expand the Web site that your OWA users use to access their Exchange server. By default, this Web site will be the Default Web Site.
      4. Go to step 5.
  5. Right-click the CustomErrors folder, and then click Properties.
  6. Under the Application settings section, click Create.

    Make sure that CustomErrors is displayed in the Application name box.

    Note For Exchange 2003 running on IIS 6.0, click ExchangeApplicationPool in the Application Pool list.

  7. Click the Documents tab, and then add the Owahttps.asp file to the Enable default content page. Move the Owahttps.asp file to the top of the list.
  8. Click the Directory Security tab, and then click Edit under Authentication and access control.
  9. Click to select Enable anonymous access, and then click OK.
  10. Under Secure communications, click Edit.
  11. Click to clear the Require secure channel (SSL) check box, and then click OK two times.
  12. Right-click the Exchange virtual directory, and then click Properties.
  13. Click the Custom Errors tab, and then double-click 403.4.
  14. In the Message Type list, click URL.
  15. In the URL box, type /CustomErrors/Owahttps.asp, and then click OK.
  16. Click the Directory Security tab.
  17. Under Secure Communications, click Edit.
  18. Click to select the Require secure channel (SSL) check box.

    Note If you want to require 128-bit encryption, click to select the Require 128-bit encryption check box.

  19. Click OK two times.

    Note The Exchange virtual directory and the Public virtual directory are the only virtual directories that you have to configure to require SSL. If you have other virtual directories for which you want to require SSL, enable SSL on each virtual directory individually.

After you follow these steps, visit the http://<server_name>/exchange Web site. In this address, server_name is the name of the Microsoft Internet Information Service (IIS) server.

You should be automatically redirected to https://<server_name>/exchange and to the Logon.asp page.

Additionally, if you want to modify the IIS Default Web Site so that clients can access the OWA logon page by typing only http://<server name> instead of typing http://<server name>/exchange, follow these steps.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Start the Microsoft Management Console (MMC) IIS snap-in.
  2. Right-click Default Web Site, click Properties, and then click the Home Directory tab.
  3. Under When connecting to this resource, the content should come from, click A redirection to a URL.
  4. In the Redirect to box, type /exchange.
  5. Under The client will be sent to, click A directory below this one.
  6. Stop and start the Default Web Site.

For more information about how to simplify the OWA URL, visit the following Microsoft TechNet Web site:

http://go.microsoft.com/fwlink/?LinkId=130623 (http://go.microsoft.com/fwlink/?LinkId=130623)

APPLIES TO
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange 2000 Enterprise Server
  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition
Keywords: 
kbinfo KB839357

Outlook Quick Address Type

Wednesday, June 17th, 2009

To fix this up, search for a .NK2 file, this is the file used to store quick contacts (suggested names) etc.

It will depend on your O/S as to where this file is, search will help you but if it is an XP machine you will find it here.
C:\Documents and Settings\%USER PROFILE%\Application Data\Microsoft\Outlook\

Note: this is a hidden file, so you may need to go into Folder options and change the setting to View hidden files.

Copy this file over to the same directory but on the new computer, and it should work!

NDR Has Long Reply To Email Address

Monday, June 1st, 2009

Maybe you have seen this or something similar: MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@yourdomain.local

This has been confirmed by Microsoft as a problem with exchange 2007 update rollup 7, this is being resolved in next version.

Learn more here if you dont believe us: http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/166f6cbd-cb1f-494c-aff4-dee3c4b20714

Thanks

  • About Me

    A little something about you, the author. Nothing lengthy, just an overview.

  • You are currently browsing the Fruit Box I.T blog blog archives for June, 2009.