We have ProIV 5.5 running on a virtual server instance (VMWare ESX 3.5) running Windows 2003 and MS SQL 2000 on the same server as a test environment. In general, the performance of the entire server is less than a physical server but have not seen any indications of problems of ProIV communicating to SQL Server. We have not done any tuning/tweaking of ProIV or SQL settings.
Fred
- ProIV Resource Centre
- → Viewing Profile: Posts: Fred Marker
Community Stats
- Group Members
- Active Posts 82
- Profile Views 6,272
- Member Title Advanced
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Male
-
Location
Columbus, Ohio, United States
Previous Fields
-
First Name
Fred
-
Surname
Marker
-
Year Started ProIV
1984
-
Highest ProIV Version Used
5.5
-
Company Working For
Ohio State University
0
Neutral
User Tools
Latest Visitors
Posts I've Made
In Topic: ProIV on Windows on a VMWare VMX host
11 February 2009 - 01:54 PM
In Topic: PRO-IV and Virtual Servers
07 July 2008 - 08:55 PM
Tony,
Sorry for the long delay in my response. I've had family medical emergencies.
We have VMWare ESX running on 64-bit HP servers with a EMC SAN. I don't have the details on cpus and memory.
Fred
Sorry for the long delay in my response. I've had family medical emergencies.
We have VMWare ESX running on 64-bit HP servers with a EMC SAN. I don't have the details on cpus and memory.
Fred
In Topic: Terminal Services Printer Mapping
07 July 2008 - 08:47 PM
Are you trying to print to a printer attached to a Windows computer (local) that is running the Remote Desktop Client connected to another Windows computer (remote) where the ProIV client is running?
Depending on the policies of your network, local printer mapping might be disabled for some or all remote connections.
Depending on the policies of your network, local printer mapping might be disabled for some or all remote connections.
In Topic: Host Closed Connection
07 July 2008 - 08:22 PM
We are running 5.5 rev 543 on Windows 2003 Server and have experienced a similar problem, very intermittently, where ProIV kernel did not fully start after a server restart. No errors, logs or other evidence to explain the reason/cause.
Many years and ProIV versions ago, we did run a weekly scheduled restart of our ProIV server which seemed to help keep ProIV running smoothly. Since abandoning that practice, our ProIV server has been stable. There have been a few times when only a server restart would correct a ProIV kernel problem.
Many years and ProIV versions ago, we did run a weekly scheduled restart of our ProIV server which seemed to help keep ProIV running smoothly. Since abandoning that practice, our ProIV server has been stable. There have been a few times when only a server restart would correct a ProIV kernel problem.
In Topic: PRO-IV and Virtual Servers
05 June 2008 - 06:54 PM
We have ProIV 5.5r543 operational for almost 6 months on a virtual machine running Windows 2003 server as our development, test and training environment without any issues or problems. We will be migrating our production ProIV server to a virtual machine later this year.
- ProIV Resource Centre
- → Viewing Profile: Posts: Fred Marker
- Privacy Policy
