Moving from XP to Windows 7 with client side.
Running into a couple issues with Sybase 15.
1) "Interactive SQL" - many widgets in ie options are defective or missing
2) When running simple query get Swing/AVT widget exception error.
Anyone ran into or worked thru any issues moving to 7?
Other versions of the Windows app, but not 7. As you may be aware 7 is only slightly more reliable than Vista.
Those messages are classically due to (a) Sybase Client (SybaseCentral; InteractiveSQL, the GUI utilities) all using the Java VM and (b) that not being successfuly installed.
Get the Sybase Client CD, and install again. Do not Customise, use the Default installation options. Watch the progress for errors. Ensure the JVM installation succeeds. You may have to retrieve any missing files from the Windows 7 CD.
Otherwise open a Support Case.
Related
I have 2 computers running Domino Designer, On my new one I get java errors in a server based application and not on the old one.
I have installed the required package on both machines and I have the same compiler set in prefs.
The computer with errors is a new one running windows 10 and DDE 11.0.1 FP1 and the old one is running Windows 7 and DDE 11.0.1
there is probably some paths or something that I have forgotten to set but can't find it.
what can be the cause of these errors on my new machine?
Check your target platform settings as blogged by Jesse Gallagher: https://frostillic.us/blog/posts/058650E080E352178525832B00519D2C.
Windows 10 comes with IIS 10, and ColdFusion 10 doesn't seem to like it. ColdFusion 10 installs fine, but when it comes time to create connectors (either during installation or by using the tool at C:\ColdFusion10\cfusion\runtime\bin\wsconfig.exe), it fails. The error message I get is that it doesn't support IIS 10.
This connector is required to set up the CFIDE and jakarta virtual folders in IIS.
Any way around this?
An already deleted blog post from blogs.coldfusion.com (http://blogs.coldfusion.com/post.cfm/configuring-connectors-manually-for-iis-10) once stated the following
With Windows 10 out, there is a problem that most of the ColdFusion
customers will face, configuring connectors for IIS 10. Wsconfig, the
connector configuration tool, only supports till IIS 8.x. While the
ColdFusion team is working on this issue and will try to provide the
fix for it as soon as possible, there is already a KB article which
can be referred for configuring the connectors manually. Although the
article was originally written for CF10, it can be used for CF11 also.
After following all the steps in the article, you need to do one more
thing. Add index.cfm as default document for your website in IIS.
This solution is only recommended for development environments as
through testing of the connectors with IIS 10 is still going on. So
for production machines, you should wait for the actual release from
Adobe.
UPDATE
Important update: Note that ColdFusion 10 and 11 have been updated to
support Windows 10, a couple months after this blog post was first
written. Consider applying that update rather than this manual
configuration.
If you are running Windows 10 Pro, you also have the option of running a Virtual Machine in the included Hyper-V offering. Instructions on how to enable Hyper-V are found here: http://blogs.technet.com/b/canitpro/archive/2014/10/02/step-by-step-creating-and-running-a-windows-10-vm-on-windows-8-1.aspx
Simply spin up a version of Windows required.
apply latest hotfix for cf 11 hotfix_019.jar. that will fix the issue above
I know this isnt a dev question per se, but is there a timeline on a 5.2 build that can be installed on Win 10?
I think the issue i am seeing is just with the installer so an in place upgrade to Win 10 might work fine, but a clean install fails as it doesnt acknowledge IIS 10 or whatever version comes with Win 10.
Thanks!
Official answer - Windows 10 is not yet supported by the currently available Acumatica ERP installers, however the issue has already been fixed internally (AC-56069 - fixed in 4.20.2262, 5.10.0785, 5.20.1012 and newer). Following workaround can be used in the meantime:
Download the Orca tool to edit the MSI file: http://adriank.org/wp-content/uploads/2015/01/Orca.zip
Open the
MSI file using this tool (might be able to right click on MSI and
open with Orca)
Go to the LaunchCondition table
Drop/delete the IIS version condition (inside MSI, the LaunchCondition entry is IISVERSION >="#7"; system does a string comparison and "10" is
smaller than "7")
Save and close Orca
Run the setup
I can't give you an "official" answer but I can give you a work around.
If you download a utility called LessMSI you can extract the installation files. They will come out in a folder called "SourceDir". Simply take these and replace the files in your default installation folder or run them from another location.
Then you can proceed as normal.
The installer only checks if pre-reqs are installed and then copy's the files to the output location. If you have IIS already setup with dotnet support then the rest will be fine.
I do this frequently if I have to install a site with a specific version in order to upgrade or test a client's snapshot.
I have 4.1,4.2,5.1,5.2 running on my Windows 10 workstation as I type
I install my EF5 winforms application using Click Once.
When I installed on a Windows 7 virtual computer it worked correctly, however when I installed on a Windows XP virtual computer I got an "underlying provider failed on open" error.
I consulted this link and decided to look at the Distributed Transaction Coordinator in component services on the XP computer..
I only viewed things in component services, by expanding the tree.
Now my application works, and I don't understand why it didn't or why it is fixed.
Can anyone explain this to me?
When install SQL Server 2000 (Evaluation copy) on Windows 7 32 bit Home Premium desktop computer,
system gives the following error and Installation not successful:
InstallShield Engine has stopped
working A problem caused the program
to stop working correctly. Windows
will close the program and notify you
if a solution is available.
Sql server 2000 is not supported on Windows 7. You might be able to get it installed but you would have problems.
According to this blog posting you even need SP3 of Sql Server 2005 for it to work on Win7.
http://blogs.msdn.com/sqlreleaseservices/archive/2009/10/23/sql-server-on-windows-7-and-windows-server-2008-r2.aspx