I am having problems setting up my IIS to allow the (data) pump to work.I have been through the msdn articles repeatedly (and Atanas' blog).
I am running Win7/64bit and SQL2008-R2(64b)
my problem is not one of security - I have all the services configured to use the same account and confirmed access -but rather when I hit the url http://localhost/olap/msmdpump.dll the browser forces me to attempt to download - it is as if the isapi script handler is not being respected/enforced.
I have tried this on 3 machine and all are acting the same. I must be missing a step somewhere - but I have read/re-read the articles again and again following along meticulously.
any ideas?
yes- I discovered I had placed the extension only and not included the wilcard symbol.Closer inspection revealed that .dll is not the same as *.dll
This is now working great.
Thank you
Hello,
This most definitely is a problem with the server not knowing how to handle the *.dll filetype. What I would do is make sure that I have the proper scripts mappings in addition to the isapi script handlers.
Open Handler Mappings in the IIS Manager and see if you have the *.dll mapping enabled. Its name is also important. It should be the same as the name of your app holding the msmdpump.dll. I'd recommend deleting it if its there and recreating it. This would allow you to create automatically the ISAPI related stuff too. After you have verified the mappings go to ISAPI and CGI restrictions. In there verify the olap restriction is set to Allowed.
These two things should fix your problem.
All the best,
Atanas