Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Issue with MS SQL 2008R2 Replication on IIS7 (Win 2008 SBS)

Options
  • 02-12-2010 11:22pm
    #1
    Seth Brundle
    Moderators, Politics Moderators Posts: 39,853 Mod ✭✭✭✭


    I'm trying to set up replication on a server here and can't get it going in IIS.

    I can't get it to properly load the replisapi.dll file required by the replication process.

    All privileges for various users have been set up ono both the directory and files.

    Currently the issue is as follows:
    Detailed Error Information Module IsapiModule Notification ExecuteRequestHandler Handler ISAPI-dll Error Code 0x800700c1
    Requested URL https://localhost:9989/SQLListenerdll/replisapi.dll Physical Path C:\inetpub\replication\SQLListenerdll\replisapi.dll Logon Method Basic Logon User XXXXX

    Most likely causes:
    • IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
    • IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
    • IIS was not able to process configuration for the Web site or application.
    • The authenticated user does not have permission to use this DLL.
    • The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

    Things you can try:
    • Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
    • Check the event logs to see if any additional information was logged.
    • Verify the permissions for the DLL.
    • Install the .NET Extensibility feature if the request is mapped to a managed handler.
    • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
    Of the "Things you can try", I've done them all except the last (which required deleting everything within the wwwroot folder which I simply can't do.

    Any ideas?


Advertisement