I'm trying to get a legacy Powerbuilder 8 application to work in a Windows 10 environment. The application has not been installed from any installation package, I simply open it from a network share containing all the necessary files. It works this way in Windows 7 systems. In Windows 10 the app opens fine, but connecting to database fails with error message:
999: DBMS MSS is not supported in your current installation.
Neither Windows 7 nor Windows 10 workstations have any specific database access drivers installed.
My development environment has Windows 10 and there connection to the database works ok. The database server is installed locally in the dev environment, though.
We had a problem with Powerbuilder 8.4 and 0racle 10 and 11. With Windows 10 patch 1803. When we copied files to local drive it worked. We were getting strange data base error. It had to do with smb version 1. June 30 2018 Windows 10 solved the problems. If your still having problem this may be worth a shot.
Related
i installed SQL Developer on my MacBook
when i tried to run the sql code it says must create new connection
it required username/password
so how can i solve this
before i was using oracle database XE 12 on windows 10
but now i am using macOS and i see i cant use this software anymore (oracle database XE 12)
so i tried to install SQL Developer
Oracle SQL Developer is a tool that lets you connect to an (Oracle) database. But - you have to have the database as well (apparently, there's none on your Mac).
Express Edition database you previously used on Windows 10 was (probably) 11g (not 12; it doesn't exist), but it woks on Windows an Linux - not macOS.
Moreover, none of the modern Oracle databases can be installed on Mac; the last one was, I think, 10g (but - as it is out of support, you can't even download it any more).
Therefore, you could install a virtual machine on Mac, put Windows OS onto it, download and install 11gXE along with SQL Developer and use it.
But, why bother? Install VirtualBox and then download one of Pre-Built Developer VMs (for Oracle VM VirtualBox).
I'd like to install MongoDB Community Edition on my computer, which has the 64-bit Windows 10 Home OS, but the system requirements say I need Windows Server 2008 to do it.
I don't think my computer has Windows Server 2008. Is there any way around this? For example, would it work for small-scale databases, or is it totally incompatible without Windows Server 2008?
If I absolutely can't use MongoDB, is there another non-relational database that would work with my system? (It would have to be free.)
I admit that the download site is a bit confusing.
But you can simply download the MSI and install it on your Windows 10 machine. A Windows Server version is not required for the community edition.
Disclaimer: I have it on a Pro (Windows 7 and 10, without Windows 2008 or any other server) edition, not on a Home edition, but I'm pretty sure that it will work in the local machine context)
I installed parallel 9 with Windows 10 images installed on mac.
When I try to share mac folders to windows 10 manually I encounter following error
"Parallels mounter is unable to open the virtual hard disk".
Following document : http://kb.parallels.com/en/112609 to do mannually installation.
It fails because Parallel 9 does not support Windows 10. After upgrade to Parallel 12 and re-install Win 10. Everything goes fine.
I am working with a client that is running Filemaker Server 5 in a workgroup environment and is now upgrading to a true client server network running either MS windows server 2008 or 2012. Will Filemaker Server 5 run in the new network environment. They do not want to upgrade Filemaker. Any help would be greatly appreciated
Have a look at this:
FileMaker Server operating system requirements - all versions
Windows 2008 does not appear on the list until FileMaker 10. Windows 2012 only supported only with FileMaker 13.
This is an official supported version chart, so you still can try and install it. I am sure, there is a compatibility mode which will let you run it. If you have any problem, you will not be able to get any support from FileMaker.
If updating FileMaker is such an issue, you might be better of running a VM on the same server with an older OS and serve it from there.
You will probably have a similar problem with clients' installs when their workstations are upgraded. FileMaker 15 is around 15 years old.
You should also consider that the filemaker 5 / 6 clients will not install on a new OSX OS Version - I'm not sure about Windows, that should be tested before moving forward if that is a requirement.
All new versions of Filemaker will convert Filemaker 5 files to a new format, however it's a big change and the scripting and layouts need to be checked after conversion. Filemaker 5 is 14+ years old and support stopped around 10 years ago which explains the compatibility issues.
I am running tests successfully on Windows XP but not even got a single successful build while running through Windows 2003.
Any one knows whether it is compatible or not as I read on some site that WatiN is fully tested on XP and not on other Windows editions.
I'd ordinarily post this as a comment on Sam's answer, but I'm trying to make a stack trace searchable, so here goes...
WatiN.Core.Exceptions.IENotFoundException : Could not find an IE window matching constraint: Timeout while waiting to attach to newly created instance of IE.. Search expired after '30' seconds.
at WatiN.Core.IE.CreateIEPartiallyInitializedInNewProcess()
at WatiN.Core.IE.CreateNewIEAndGoToUri(Uri uri, IDialogHandler logonDialogHandler, Boolean createInNewProcess)
at WatiN.Core.IE..ctor(String url, Boolean createInNewProcess)
c:\...\WithVendorSite.cs(42,0): at WithVendorSite.VerifyCanLogIn(TargetSite target)
I developed my test on Windows 7 against WatiN 2.0.10.928 but the test was continually getting stuck with a blank browser with about:blank in the address bar when run on Windows Server 2008 with latest WUs, and Enhanced Security Configuration turned off and running the tests elevated (Run as Administrator).
The problem in my case (thanks Sam) was the absence of Microsoft.mshtml.dll in the bin directory (I had figured out Interop.shdocvw.dll was necessary from error messages I'd encountered on the Windows 7 side).
After adding Microsoft.mshtml.dll, things run happily with ESC turned back [but the test process needs to run elevated].
I run our WatiN integration test suite (hundreds of tests) on Windows 2003 with IE6. Works fine, no special tricks done. What is the exception you are getting? Are you sure mshtml.dll (the COM dll somewhere in the windows directory) is registered correctly on this machine? Do you have the Microsoft.mshtml.dll (interop assembly) and interop.shdocvw.dll in the same directory as WatiN.Core.dll?
Update: Its officially supported, from the faq
Which windows versions are supported?
Windows 2000, Windows XP, Windows 2003
and Windows 2008.
Original post:
I use it on vista all the time. I haven't used it on windows server 2003 though.
Have you tried logging on interactively into the server and trying to run the tests manually? It may be because of the account that your build server is running under or some particular security settings you have setup. Have you checked to see if IE is stopping you from viewing the page due to it not being in the trusted sites list?
I was using Watin 1.3 on Windows XP but the same on Win 7 having problem....
Officially Watin 1.3 works on O.S. Xp and earlier on Win XP
But Watin 2.1 works fine on Win 7 and XP.
Officially Watin 2.1 supports any Microsoft O.S.