I have a analysis server database that runs Windows Server 2008 64 bits. And users reach cubes by msmdpump.dll. There is any problem before used FileMaker on same server. I could not analysis server database. I searched some documents that say I must change the application pool to 32 bit enabled. I changed OLAP web.config and added ISAPI filter. Also I read that I should use 32 bit msmdpump.dll but I run IIS 64 bit and how could you find 32 bit dll. Now I can not reached in any way. Could you help me what steps need to follow?
To install and configure OLAP Pump for IIS x64 connecting to an SSAS x64 instance, you use the msmdpump.dll of your x64 SSAS installation dir. To access an SSAS x86 instance, you use the msmdpump.dll of your x86 SSAS installation dir. The second variant requires you to enable 32 bit on your application pool.
A very nice guide of how to set up SSAS access via IIS can be found here:
Microsoft - Configure HTTP Access to SSAS via IIS
Many thanks and best regards
Related
I have a classic ASP application which I've moved from a Windows 2003 server running IIS6.0 to 64-bit Windows 2008 R2 running IIS7. In IIS7 I've created a website and added an application to that and have set the application pool to enable 32-bit applications.
The application connects to an Oracle database using the ORAOLEDB driver - I've installed the 64-bit Oracle client 11.2.0.3 to connect to the backend Oracle 11g database and can connect fine via the same user as the application using SQLPlus.
When I run the application though, its attempt to connect to Oracle fails with the IIS logs showing the error:
"Provider cannot be found. It may not be properly installed"
I've tried various possible things to try and get this working:
registering OraOLEDB11.dll manually
disabling 32-bit applications from the app pool
using the 32-bit drivers instead both with 32-bits apps enabled and disabled
reinstalling the drivers completely and trying all the above
So far without any luck. The asp code connects as follows:
objOracleConnection.CursorLocation = adUseClient
objOracleConnection.ConnectionString = "Provider=OraOLEDB.Oracle;Data Source=MYDATASOURCE;User ID=USER;Password=PASSWORD;PLSQLRSet=1;OLE DB Services=-2;"
objOracleConnection.Open
EDIT: I've tried a simple VBS script (using essentially the same code as above) to connect and it gets the same error, so IIS may not be the problem. The exact same script works on the Windows 2003 box however.
I've reinstalled the Oracle client via the 'Troubleshoot Compatibility' option, indicating that the application works under Windows 2003 SP1 but still get the same issue from both the VBS script and the IIS application :(
This is an educated guess, but enabling 32 bit applications in IIS7 seems to disable 64 bit applications. If it's a 64 bit driver you may need to disable 32 bit in your app pool
My application is in classic asp. Till now it is working fine with 32bit windows server and connecting oracle via a system DSN which is prepared with "Microsoft ODBC driver for oracle".
Now, the server has been migrated to 64bit Windows server 2008 R2. We have some third party dlls, which also have 64bit available. So, I deploy the application in IIS 7.5 and it is working fine.
In new server, I am using Oracle driver, as for 64bit, there is no driver of "Microsoft ODBC Driver For Oracle". Everything is working fine, except, when I try to fetch a record-set, it is returning nothing. No Error message, no data, nothing is coming.
Also, I can't change the app pool compatibility with 32 bit to "True", because, there are some third-party component which will only work in either of one environment. Either 32 bit or 64 bit.
So, my concern is, whether I can work with both the DSN[32 and 64]? OR any other idea to run the application.
Could you use an OLEDB driver instead. Oracle certainly provide a 64 bit OLEDB driver, and it could well be installed on your server already.
http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
Here's another useful link, with a very friendly URL
http://www.connectionstrings.com/oracle/
ODBC isn't generally regarded as the best way to go, unless you're using MySQL when it's pretty much your only option
I've got stuck with strange Oracle connection error on Windows Server 2003 x64 (IIS 6)
While console .Net application that runs onbehalf of administrator successfully connects to Oracle 10g Express via OleDb [Connection string looks like: Provider=MSDAORA;Data Source=server-ip:port;User Id=user;Password=password;]
ASP.NET 4.0 web-site (application pool runs on behalf of administrator too) fails with error:
The 'MSDAORA' provider is not registered on the local machine
Connection string is the same, but it doesn't work for asp.net site. What shall I check?
Thank you in advance!
This Social.MSDN link seems to point to the fact that you have x86 drivers installed;
From my viewpoint you have two options:
Convert the app to run on 32bit mode in IIS - Can help if you require assistance. LINK
Download and try the 64bit version of the drivers. Oracle x64 downloads
Another approach would be to enable 32-bit applications for the IIS Application Pool your application is using. I would suggest creating a new application pool specifically for your application making sure to enable 32-bit applications.
You'll likely suffer performance issues but at least you'll be up and running.
I have resolved this issue in one of my applications with ASP(MSDAORA connection) - oracle environment with following fix from
http://technet.microsoft.com/en-us/library/cc784046.aspx
following are the steps
To enable IIS 6.0 to run 32-bit applications on 64-bit Windows
1.Open a command prompt and navigate to the %systemdrive%\Inetpub\AdminScripts directory.
2.Type the following command:
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true
3.Press ENTER.
In my ASP.NET application I have ftpdata folder, there is an MS Access 2010 file e.g. somename.accdb.
On my local computer (Win XP), there is no problem to connect with OleDb to this file and read write datas into and from tables.
But on server (Windows Server 2008), I cannot connect to the same file like on localhost.
Can you help me, please, where problem could be?
Finally, I found solution of problem.
There was not installed 2010 Data Connectivity Components on the server.
The windows user that your application pool is running in does probably not have read access to the directory/file
You need either direct access through the file system or SMB networking access (via a share defined on the server). If the FTP folder has an SMB share name, use that to get to it, but it's likely not shared (since it's purpose is for FTP access, not SMB access).
Installing the 2010 Data Connectivity Drivers does not seem to work, what worked for me was to set the corresponding website application pool in IIS to enable 32-Bit applications.
Official Microsoft Reference:
I know it depends, but I am just curious what specifications others are using to run a simple site with a MS SQL Server back-end. What is recommended for the application, not the database?
If you're not talking about the database, I would say that running a simple MVC web application you would just need enough RAM to run whatever Windows OS you plan on deploying it under. You shouldn't need any more than the recommended amount.
So for example, here are the Windows Server 2008 requirements.
Would have to agree with Joe, the recommended RAM for running the OS should be sufficient. However, when you start to use resource hungry tools like SQL Server I would always recommend adding at least 1 GB.
You can run a simple MVC site on Windows XP with IIS 5.1 and SQL Server 2005 Express. Here are the system requirements for Windows XP.
RAM is so cheap now I would go with at least 2 GB.