4D 2003 running on Windows 2008 Server?

Randy Engle (2/8/10 5:00PM)
Brad Perkins (2/8/10 5:05PM)
Jody Bevan (2/8/10 6:22PM)
Randy Engle (2/9/10 8:22AM)
Mike Vogt (2/9/10 8:29AM)
Brad Perkins (2/9/10 8:33AM)
Randy Engle (2/9/10 9:09AM)
Brad Perkins (2/9/10 9:17AM)
Alan Chan (2/9/10 9:51AM)
Lutz Epperlein (2/9/10 11:45AM)
David Dancy (2/9/10 12:09PM)
Lutz Epperlein (2/9/10 5:34PM)
Randy Engle (3/17/10 7:35PM)
Alan Chan (3/18/10 12:02PM)

Randy Engle (2/8/10 5:00 PM)

Hi Brad,

I was able to get 2003 to run on 2008 Server the first time I tried.

Thereafter, it would quit on startup.

I'm sure it's some kind of windows security thing.  I'd love to know
what it
is if you find it.

Thanks

Randy Engle

-----Original Message-----
From: 4d_tech-bounces@...
[mailto:4d_tech-bounces@... On
Behalf Of Brad Perkins
Sent: Monday, February 08, 2010 4:06 PM

We're facing a server hardware replacement for a system that is still
on
4D 2003 (hopefully upgraded to v11 by mid-year).

While I'm sure 4D 2003 wasn't certified to run on it has anyone had
problems running 4D 2003 on Windows 2008 Server?

Thanks,

Brad Perkins
Brad Perkins (2/8/10 5:05 PM)

We're facing a server hardware replacement for a system that is still
on
4D 2003 (hopefully upgraded to v11 by mid-year).

While I'm sure 4D 2003 wasn't certified to run on it has anyone had
problems running 4D 2003 on Windows 2008 Server?

Thanks,

Brad Perkins
Jody Bevan (2/8/10 6:22 PM)

Brad:

We have several 4D 2003 based systems running on Windows 20008 64 bit.

Jody

On 8-Feb-10, at 5:05 PM, Brad Perkins wrote:

color><param>00000,08CF,D8CC/param>WWe're facing a server hardware
replacement for a system that is  
still on
4D 2003 (hopefully upgraded to v11 by mid-year).

While I'm sure 4D 2003 wasn't certified to run on it has anyone had
problems running 4D 2003 on Windows 2008 Server?

Thanks,

Brad Perkins
/color>
Randy Engle (2/9/10 8:22 AM)

I'm wide open to any other suggestions to get 4D 2003 working on
Windows
2008 Server (Service Pack 2).

What I've tried:

I've Turned DEP Off
I've Turned DEP on, with my 4D app on the list.

I've set the app to run in "compatibility" mode for both XP and 2003
Server

I've turned User Account Control On
I've turned User Account Control Off

I'm running my 4D App as "Administrator"

I've moved the data file to various locations I've deleted the
preferences
files

I've chanted some Krishna
I've thrown salt around the room
I've smudged the room for evil spirits
I've sacrificed a lamb as an offering (it was actually an old stuffed
pig
that my daughter used to play with...)

As I stated earlier, It started the first time I installed it,
thereafter,
it quits right away with a message, that the app has "stopped working".

Any other ideas?

Many, many thanks.

Randy Engle

-----Original Message-----
From: 4d_tech-bounces@...
[mailto:4d_tech-bounces@... On
Behalf Of David Dancy
Sent: Monday, February 08, 2010 5:10 PM

Randy

Check your DEP settings. You may need to add 4D to the list of
exceptions,
or turn off DEP altogether (I think it's on by default).

Brad
We run v2003 on Windows 2008 server. For 4D Server, check out some
recent
threads about how to get the admin window to work properly when you're
running it as a service. Running it as an application should be no
problem.

Others may have relevant experience of whether the 64-bit version
supports
4D 2003. We always require our users to have 32-bit Windows just to be
on
the safe side. We've had various issues with printer drivers
(especially
converting to PDF) on 64-bit systems. If you can figure out where
32-bit
DLLs and so on have to go on your 64-bit system you may have better
success.

HTH

David Dancy
Sydney, Australia

On 9 February 2010 12:00, Randy Engle <randy.engle@...
wrote:
color><param>00000,08CF,D8CC/param>HHi Brad,

I was able to get 2003 to run on 2008 Server the first time I tried.

Thereafter, it would quit on startup.

I'm sure it's some kind of windows security thing.  I'd love to know

what it is if you find it.

Thanks

Randy Engle

/color>
Mike Vogt (2/9/10 8:29 AM)

Brad,
Tests of our 4D2003 application running on Win2008 Server show that
the app itself runs fine, but starting a backup using either 4D code
or the server backup menu choice immediately crashes the app.  We
have
been unable to deploy because of this.

Mike Vogt
Willsub

color><param>00000,08CF,D8CC/param>

Date: Mon, 08 Feb 2010 17:05:57 -0700
From: Brad Perkins <bperkins@...

We're facing a server hardware replacement for a system that
is still on
4D 2003 (hopefully upgraded to v11 by mid-year).

While I'm sure 4D 2003 wasn't certified to run on it has anyone had
problems running 4D 2003 on Windows 2008 Server?

Thanks,

Brad Perkins

/color>
Brad Perkins (2/9/10 8:33 AM)

Alan,

It will be awhile before we have the new server and have it setup so I
won't have an answer anytime soon.  I asked in case I needed to
push
for
a purchase approval that would allow Windows 2003 Server which is what
we run now (very solid).

It sounds like you and Randy can't run 4D 2003 Server on a Windows 2008
Server, but others can, so it might be better to ask them what they are
doing different. Thanks to everyone else who responded that they've had
success. That is reassuring.

Brad Perkins
color><param>00000,08CF,D8CC/param>MMessage: 10

Date: Tue, 09 Feb 2010 09:51:53 +0800
From: "Alan Chan" <alan@...

Randy,

We got exactly the same behavior. We want to know what Brad find out
too.

/color><color><param>FFFFF,0000,0000/param>II was able to get 2003 to
run on 2008 Server the first time I tried.

Thereafter, it would quit on startup.

I'm sure it's some kind of windows security thing.  I'd love to
know
what
it
is if you find it.
/color><color><param>66ED5,0479,7042/param>
/color><color><param>00000,08CF,D8CC/param>
David,

Without turning off DEP, you can't even run on Win server 2003 either.

/color><color><param>FFFFF,0000,0000/param>CCheck your DEP settings.
You may need to add 4D to the list of
exceptions, or turn off DEP altogether (I think it's on by default).
/color><color><param>66ED5,0479,7042/param>
/color><color><param>00000,08CF,D8CC/param>
Alan Chan

/color>
Randy Engle (2/9/10 9:09 AM)

Not Using 4D Backup.

This is an OEM app.  We have over 200 server installations

We are working as fast as we can to get upgraded to 2004 or v11

A fix in the interim would be great, as many of our customers are
moving to
2008 server.

Randy Engle
[Randy Engle Responded:]

Do you use 4D Backup?
As I already stated in another posting don't integrate the log file in
your backup project! It will lead to a crash very reliably in the above
mentioned environment. Or don't use the backup at all.

If this isn't an option for you, upgrade at least to 4D 2004.

If you don't use backup already I haven't any glue .... :-(

Lutz
Brad Perkins (2/9/10 9:17 AM)

Mike,

You didn't mention via the backup scheduler? Is that a problem too? Not
being able to backup would be a show stopper for us.
To others who are running Win2008 server with some success, are you
also
having this problem?

Thanks,

Brad
color><param>00000,08CF,D8CC/param>BBrad,
Tests of our 4D2003 application running on Win2008 Server show that
the app itself runs fine, but starting a backup using either 4D code
or the server backup menu choice immediately crashes the app.  We have
been unable to deploy because of this.

Mike Vogt
Willsub
/color>
Alan Chan (2/9/10 9:51 AM)

Randy,

We got exactly the same behavior. We want to know what Brad find out
too.

color><param>00000,08CF,D8CC/param>II was able to get 2003 to run on
2008 Server the first time I tried.

Thereafter, it would quit on startup.

I'm sure it's some kind of windows security thing.  I'd love to know
what
it
is if you find it.
/color>
David,

Without turning off DEP, you can't even run on Win server 2003 either.

color><param>00000,08CF,D8CC/param>CCheck your DEP settings. You may
need to add 4D to the list of
exceptions, or turn off DEP altogether (I think it's on by default).
/color>
Alan Chan
Lutz Epperlein (2/9/10 11:45 AM)

Beside the DEP problem, we experienced a different problem with 4D2003
Server and Windows Server 2008:

Integrating the log file into 4D backup leads to a crash of 4D Server
2003.

The workaround:
* Don't use the log file
* Or don't incorporate the log file into the 4D Backup.

Regards
Lutz

--
Lutz Epperlein                     
     ICQ 357452375
Intranetz - Gesellschaft für Informationslogistik mbH
Berlin
Germany
David Dancy (2/9/10 12:09 PM)

Randy

Check your DEP settings. You may need to add 4D to the list of
exceptions, or turn off DEP altogether (I think it's on by default).

Brad
We run v2003 on Windows 2008 server. For 4D Server, check out some
recent threads about how to get the admin window to work properly when
you're running it as a service. Running it as an application should be
no problem.

Others may have relevant experience of whether the 64-bit version
supports 4D 2003. We always require our users to have 32-bit Windows
just to be on the safe side. We've had various issues with printer
drivers (especially converting to PDF) on 64-bit systems. If you can
figure out where 32-bit DLLs and so on have to go on your 64-bit
system you may have better success.

HTH

David Dancy
Sydney, Australia

On 9 February 2010 12:00, Randy Engle <randy.engle@...
wrote:
color><param>00000,08CF,D8CC/param>HHi Brad,

I was able to get 2003 to run on 2008 Server the first time I tried.

Thereafter, it would quit on startup.

I'm sure it's some kind of windows security thing.  I'd love to know
what it
is if you find it.

Thanks

Randy Engle

-----Original Message-----
From: 4d_tech-bounces@...
[mailto:4d_tech-bounces@... On
Behalf Of Brad Perkins
Sent: Monday, February 08, 2010 4:06 PM

We're facing a server hardware replacement for a system that is still
on
4D 2003 (hopefully upgraded to v11 by mid-year).

While I'm sure 4D 2003 wasn't certified to run on it has anyone had
problems running 4D 2003 on Windows 2008 Server?

Thanks,

Brad Perkins

/color>
Lutz Epperlein (2/9/10 5:34 PM)

On 09.02.2010 17:22, Randy Engle wrote:
color><param>00000,08CF,D8CC/param>II'm wide open to any other
suggestions to get 4D 2003 working on Windows
2008 Server (Service Pack 2).

What I've tried:
[ .... ]
/color>
Do you use 4D Backup?
As I already stated in another posting don't integrate the log file in
your backup project! It will lead to a crash very reliably in the above
mentioned environment. Or don't use the backup at all.

If this isn't an option for you, upgrade at least to 4D 2004.

If you don't use backup already I haven't any glue .... :-(

Lutz

--
Lutz Epperlein                     
     ICQ 357452375
Intranetz - Gesellschaft für Informationslogistik mbH
Berlin
Germany
Randy Engle (3/17/10 7:35 PM)

Cc: bperkins@... alan@...

Hello Alan Chan and Brad Perkins,

FYI, I've got 4D 2003 to run successfully on Windows 2008 Server.

HOWEVER, the culprit seems to be 4D Write.  It only works if I remove
it.
Unfortunately, our app requires it.  (ouch!)

As well:
I turn off all DEP
Set the app to run in compatibility mode for Windows Server
2003,
for ALL Users,
Run as administrator.

Do your apps use 4D Write?

Let me know if you've made any other headway on this.

I think I've come to a dead end, and need to get all of our users
upgraded
to a more recent version of 4D.

;-)

Randy Engle

-----Original Message-----
From: 4d_tech-bounces@...
[mailto:4d_tech-bounces@... On
Behalf Of Brad Perkins
Sent: Tuesday, February 09, 2010 7:33 AM

Alan,

It will be awhile before we have the new server and have it setup so I
won't have an answer anytime soon.  I asked in case I needed to push
for
a purchase approval that would allow Windows 2003 Server which is what
we run now (very solid).

It sounds like you and Randy can't run 4D 2003 Server on a Windows 2008
Server, but others can, so it might be better to ask them what they are
doing different. Thanks to everyone else who responded that they've had
success. That is reassuring.

Brad Perkins
color><param>00000,08CF,D8CC/param>MMessage: 10

Date: Tue, 09 Feb 2010 09:51:53 +0800
From: "Alan Chan" <alan@...

Randy,

We got exactly the same behavior. We want to know what Brad find out
too.

/color><color><param>FFFFF,0000,0000/param>II was able to get 2003 to
run on 2008 Server the first time I tried.

Thereafter, it would quit on startup.

I'm sure it's some kind of windows security thing.  I'd love to know
/color>wwhat
color><param>FFFFF,0000,0000/param>iit
is if you find it.
/color><color><param>66ED5,0479,7042/param>
/color><color><param>00000,08CF,D8CC/param>
David,

Without turning off DEP, you can't even run on Win server 2003 either.

/color><color><param>FFFFF,0000,0000/param>CCheck your DEP settings.
You may need to add 4D to the list of
exceptions, or turn off DEP altogether (I think it's on by default).
/color><color><param>66ED5,0479,7042/param>
/color><color><param>00000,08CF,D8CC/param>
Alan Chan

/color>
Alan Chan (3/18/10 12:02 PM)

Cc: bperkins@... '4D iNug Technical' <4d_tech@...

Hi Randy,

We don't use 4D Write. You did give me a good hint about compatibility
mode for Windows Server 2003 that I wasn't aware of.

Anyway, as none of our current 2003 clients are using 2008, we would
leave
it as is. We are working hard on v11 and extremely busy digging out
compatibility issues and weekly new bugs. I hope that we could leave
2003
behind sooner.

Alan

"Randy Engle" <randy.engle@... writes:
color><param>00000,08CF,D8CC/param>
FYI, I've got 4D 2003 to run successfully on Windows 2008 Server.

HOWEVER, the culprit seems to be 4D Write.  It only works if I remove
it.
Unfortunately, our app requires it.  (ouch!)

As well:
I turn off all DEP
Set the app to run in compatibility mode for Windows Server
2003,
for ALL Users,
Run as administrator.

Do your apps use 4D Write?

Let me know if you've made any other headway on this.

I think I've come to a dead end, and need to get all of our users
upgraded
to a more recent version of 4D.

/color>
Reply to this message

Summary created 3/18/10 at 1:11AM by Intellex Corporation

Comments welcome at: feedback@intellexcorp.com