web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Axapta 3.0 and Windows 7
Microsoft Dynamics AX (Archived)

Axapta 3.0 and Windows 7

(0) ShareShare
ReportReport
Posted on by KenOwsley 395

Has anyone tried to get the Axapta 3.0 client to run on Windows 7?  I've tried all of the basics, looking so see if anyone has actually been able to make it work.

*This post is locked for comments

I have the same question (0)
  • Denis Patrakov Profile Picture
    Denis Patrakov on at
    And what's the problem running it on W7? Does it crash due to DEP or something? If it does crash beacouse of DEP then you might need to update gridex20.ocx to version 2.00.2215 or newer. You might also try setting a compatibility mode in the client's shortcut to something like WinXP SP2.
  • KenOwsley Profile Picture
    KenOwsley 395 on at

    Basically what happens is it tells me that the object server cannot be found.  I've got a specific .axc file and when I double click on it it tells me the object server can't be found.  So technically, the client is running, but Somethign about Windows 7 is blocking communication to the object server.  Ran fine under Vista...

  • Denis Patrakov Profile Picture
    Denis Patrakov on at
    If the server specified in the .axc file is available (nslookup finds it and ping can reach it) then you should try to monitor the client-server network communication. There's a handy tool for connectivity troubleshooting - Ms Network Monitor. After installation run it, make sure it's bound to the LAN adapter that AX client uses to access the AOS and click "New capture tab". There you can filter out unwanted traffic: click display filter tab and type something like 
    tcp.Port==2712
    or even 
    tcp.Port==2712 && ipv4.Address==192.168.0.100
    (or whatever IP is used by the AOS) assuming that AOS listens on the stadndard port 2712, click Apply and then click Start; then run AX client and click Stop in Netmon after the client pops up with an error message. In fact to be certain about what's going on between the client and the server you should run Netmon on the server at the same time and filter the traffic by the client's IP. Then it would be pretty straightforwarding to figure out whether packets are dropped or blocked on any side or if the client ever tries to reach the "right" AOS host. Don't forget to save the captures.
  • Trey Hart Profile Picture
    Trey Hart 40 on at

    Have you found a solution to this problem?

  • KenOwsley Profile Picture
    KenOwsley 395 on at

    Yes, I turned off the Windows Firewall.  I felt stupid when I realized that was the problem...I've not gone through any testing to figure out how to turn the Windows Firewall back on, but still allow AX to function.  I imagine I could allow the server IPs, but I haven't taken the time to do that.  I'm not overly concerned since I can have the firewall on in public locations, and off at the office. 

  • Trey Hart Profile Picture
    Trey Hart 40 on at

    awesome. Thanks!!! Maybe a rule in the windows firewall will do.  I will let you know once I start polishing up this Windows 7 client prototype.

  • KenOwsley Profile Picture
    KenOwsley 395 on at

    Do you run AX 3.0?  If so, let's trade contact info and maybe a little info about the implementation (modules in AX) and industry (what type of company).  I like to keep a few contacts here and there to ask questions of.

  • John Mawbey Profile Picture
    John Mawbey on at

    We are still running 3.0 so if anyone has any questions we can help too.  We be interested in sharing any information.

    John Mawbey

    Glenroy, Inc. Menomonee Falls, WI

     

  • Martin Vavik Profile Picture
    Martin Vavik 45 on at

    Hi!

    We also run 3.0.

    But we have to run xp for editing help files.

    Vista and w7 crashes when you try to start the editor.

    Someone who knows about the problem and maybe have a solution.

    Martin Vavik

    Hands as, Bergen Norway.


     

     

  • Sven Johannsen Profile Picture
    Sven Johannsen 10 on at

    Hi,

    to get AX (AOS) running on W7, I needed to add an incomming firewall rule UDP - source port 1212.

    Best regards, Sven 

     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans