My web application's installer does some configuration via WMI, and in order to handle different versions will ask IIS for its version with code like:
DirectoryEntry folderRoot = new DirectoryEntry("IIS://localhost/W3SVC/Info");
Version iisVersion = new Version((int)folderRoot.InvokeGet("MajorIIsVersionNumber"), (int)folderRoot.InvokeGet("MinorIIsVersionNumber"));
Server 2012 and Windows 8 both return 7.5 for this, even though the official version is 8.0. This wouldn't be so much of a problem, except that this is the same version that windows 2008 reports. Why is this, and is there a better resolution than checking the OS version?
Related
I have a Windows Server 2012 R2 with IIS 8.5, and another server with MSSQL 2012. I must install PHP in IIS and connect to MSSQL, and I don't have Internet available for Web PI.
I managed to install PHP 5.5 and I'm able to run phpinfo(), and I also assured that php.ini is being loaded from C:\php\php.ini.
I was also able to load sqlsrv driver, it reports in example sqlsrv.ClientBufferMaxKBSize 10240 10240.
But when I execute a php file that connects to DB, I get a message
This extension requires the ODBC Driver 11 for SQL Server. Access the following URL to download the ODBC Driver 11 for SQL Server for x86: http://go.microsoft.com/fwlink/?LinkId=163712
I went to that site and it says
Supported operating systems for version 3.1 of the driver include Windows Server 2012 R2`.
It says
Version 3.1 requires Microsoft ODBC Driver 11 (or higher) for SQL Serverand points tohttp://www.microsoft.com/en-us/download/details.aspx?id=36434`.
In that page, in System Requirements, WinServer 2012 R2 is not listed. When I try to install msodbcsql.msi I get message
Installation of this product failed because it is not supported on this operation system. For information on supported configurations, see the product documentation.`
Well I'm now stuck. I need PHP in WinServer 2012 R2 and IIS 8.5 connecting to MSSQL 2012. But its driver requires ODBC 11, which seems to not support latest WinServer.
Is there any hope, or will I need to wait for Microsoft to support its own OS in its own drivers?
Be sure to download the 1033\x64\msodbcsql.msi (4.4 MB) installer. Even though you are using PHP x86, you need the x64 installer since the OS is x64. I had the same issue and my app now works with PHP x86 after installing the x64 installer.
We have an ASP.net application that uses charFx 6.2. It works on windows XP clients but the clients who run Windows7 can not see the chart. Any help in this regard is really appreciated.
Thanks
The Windows 7 users probably have a newer version of Internet Explorer which is incompatible with the older version of ChartFX.
You could try to update ChartFX or run an older version of IE (through something like Citrix) on the Windows 7 machines.
I was trying to install Windows SDK which supports .NET 4.5 in a Windows 2008 server. But I couldn't find any link for the same. All I could find was this:
Windows SDK for Windows Server 2008 and .NET Framework 3.5
Can't we install SDK which supports .NET 4.5 in a Windows 2008 server, do I have to upgrade to Windows 2012 server? I could see that .NET 4.5 framework supports Windows 2008 server but not sure about the SDK. The reason I am looking for this is because, I am trying to install an assembly using GACUTIL, but when I install Windows SDK and try running GACUTIL, it states that the version is different.
Any ideas?
Got it. I was installing wrong SDK, I was installing SDK for 7.1, I should actually install SDK for 8.1. Silly mistake.
Whenever I try to install SQL Server 2012 Express with Advanced Services I am getting this error:
I have tried both version (32-bit/64-bit) and re-downloaded multiple times.
How can I solve it ?
Check if you have .Net framework 4 installed at your machine. If not - download it and install it and then try again with SQL Server.
Also check this bug at Microsoft site about .Net framework 4 (there is workaround explained in the bug).
FWIW, I just downloaded and installed SQLEXPRADV_x86_ENU.exe from HERE on a vanilla Win7Pro/64 VirtualBox virtual machine and encountered no errors.
Edit
I also installed SQLEXPRADV_x64_ENU.exe from that same location on an older Vista machine. The SQL Server installer told me that it needed some new .NET components, then it proceeded to download and install them. I didn't need to manually install anything ahead of time.
Also perhaps worth noting:
Both of the machines on which my installs were successful had no anti-virus software installed. (They are development boxes behind a firewall and I don't do email or web surfing on them.)
I'm having problems migrating a PowerBuilder application from XP to Windows 7.
We've built the application in PowerBuilder on Windows XP, and when we attempt to install components in to component services on Windows 7 machines, we get compatibility errors. Everything works great on Windows XP. But I think because the DLL's on 7 are so different, it's having problems.
If the program was built using a PowerBuilder IDE in a Windows 7 environment, would that possibly fix the problem?
The application is divided into
- a server component running on Server 2003
- a client component which installs sucessfully on Win7
- proxy components that are generated into an MSI when the server components are installed.
The problem is only the proxy. The MSI doesn't want to work on Windows 7.
Without the proxy installed on the client desktops, the client can't communicate with the server.
When I run the MSI in compatibility mode on Windows 7, I get some details of the error. Here they are
Program Compatibility Issues found Incompatible Application Fix
application CCS_Proxy_XP_Exports
Issues found Incompatible Application CCS_Proxy_XP_Exports is
incompatible.
Fix application CCS_Proxy_XP_Exports Provides steps to fix the
incompatible application. CompatMode CompatMode UserVerifySolution
User Verification of Solution Verify_NO
Detection details Collection information Computer Name: ##########
Windows Version: 6.1 Architecture: amd64 Time: Wednesday, November
14, 2012 11:56:36 AM
Publisher details Program Compatibility Make older programs run in
this version of Windows. Package Version: 1.5 Publisher: Microsoft
Windows
Program Compatibility Make older programs run in this version of
Windows. Package Version: 1.0 Publisher: Microsoft Corporation
If I view more details on the event log, I get the following
“Product: Client Communications (Application Proxy) -- Error 1928.
Error registering COM+ Application. Contact your support personnel
for more information.”
General idea
Actually dll on the win7 platform are not different from previous ones. There can be differences related to the multiple and different C runtimes that live now in the WinSxS dll-hell directories but this should not impact powerbuilder (as I can say from my 11.5 classic release experience).
I suspect that you might have some problems related to the UAC and or ACL management. I recently upgraded some legacy PB applications by adding compatibility to the Vista / Win7 specifications.
In short : the application must run without needing administrative privileges, and must not try to modify data in privileged places like c:\ or c:\windows.
Thus everything must no more be installed in program files directory. The application binaries can be deployed in program files but if the application need to create / modify some files they must be deployed in a ProgramData subdirectory for user-shared datad and / or in the local user data files for the private data. The application has to be modified to create or find the files in the correct directories. If you do not comply to the standard, the file virtualization mechanism can hide a lack of rights and can simulate the files in a VirtualStore directory in the user local data but is just a workaround and it provides some other problems.
Com+ error
Given you error messages, if the proxy is also a PB application, given the fact that PB only produce 32bits binaries and that your system is a 64bits one, maybe that the tips to register a 32b COM+ onto a Win2008 could help you?
Thought, your proxy exe/dll file does not have manifest or manifest does not contains compatibility section. Try to add compatibility info to manifest.