Dynamics AX 2009 客户端配置文件启动路径问题
我需要使用不同的配置启动 MS Dynamics AX 2009 客户端以连接到不同的 AOS。
为了实现这一点,我将客户端配置导出到 axc 文件中,效果非常好。
现在我想为我们网络中的所有客户端共享此文件,但它对某些客户端不起作用,因为由于某些有趣的原因,Dynamics AX 二进制文件的路径被硬编码到客户端配置文件中。 因此,在一台计算机上,AX 客户端安装在 C:\Program Files (x86)\Microsoft Dynamics AX\50\Client\Bin 中,在另一台计算机上安装在 C:\Program Files\Microsoft Dynamics AX\50\Client\Bin 中,该文件不起作用,因为 axc 中的路径与真实路径不同。
如何创建可在每台客户端计算机上运行的 axc 文件,以便我可以使用共享配置文件?
I need to start the MS Dynamics AX 2009 client with different configurations to connect to different AOS.
To achieve this, I exported the client configuration into an axc-file, which works pretty well.
Now I want to share this file for all clients in our network, but it does not work on some because for some funny reason, the path to the Dynamics AX binaries are hardcoded into the client config file.
So, on one computer the AX client is installed in C:\Program Files (x86)\Microsoft Dynamics AX\50\Client\Bin, on the next in C:\Program Files\Microsoft Dynamics AX\50\Client\Bin, the file does not work, since the path in the axc is different from the real path.
How do I create an axc-file which is working on every client computer, so I can use a shared config file?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(6)
我发现的唯一解决方法是在每台计算机上的某个自定义路径(例如 c:\ax)中安装客户端,而不是将其安装到程序文件中。
丑陋的。 我真的希望微软能够在未来的版本中修复这个问题。
The only workaround I found is to install the client on every computer in some custom path, like c:\ax instead of installing it into program files.
Ugly. I really hope Microsoft will fix this in some future version.
您可以使用 NTFS 中的连接点将“Program Files (x86)”指向 32 位客户端上的“Program Files”。 连接点基本上相当于 Windows 中的 UNIX 符号链接。
You can use a junction point in NTFS to point "Program Files (x86)" to "Program Files" on 32 bit clients. A junction point is basically the Windows equivalent of a UNIX symbolic link.
如果您设法将注册表项部署到客户端,那么解决方案如下:
例如: Ax32.exe -regconfig=LIVE
现在我输入这个,我意识到这个解决方案的另一个问题,这又是那些路径......但是,创建和维护两个版本的 lnk 文件很容易(一个适用于 32 位环境,另一种适用于 64 位环境)...并且注册表是相同的。
希望能帮助到你!
If you manage to deploy registry keys to the clients, then the solution is something like this:
eg: Ax32.exe -regconfig=LIVE
Now that I type this, I realized an additional problem with this solution, which is again those paths... However it's easy to create and maintain two versions of the lnk files (one for 32 and another one for 64 bit environments)... And the registry is the same.
Hope it helps!
我正在使用以下开发环境设置结构,我想这就是您正在寻找的。
下面是示例。
服务器名称:SRV01
在该服务器上为 ex 创建文件夹。 AX5 并共享该文件夹。
文件夹结构:
以下是 *.axc 文件的示例
重要提示:在每台客户端 PC 上安装 AX 2009 客户端。 安装时,系统会要求您指定 AOS - 指定任何值。 需要本地安装的 AX 2009 客户端,因为它使用 GAC 中没有的几个附加程序集。
最后 - 如何启动 AX? 只需运行 *.bat 文件即可。
希望我说得足够清楚,并希望我明白你在寻找什么))
I'm using following structure of my development environment setup and I guess this is what you're looking for.
Below is example.
Server name: SRV01
On that server create folder for ex. AX5 and share that folder.
Folder structure:
And here is example of *.axc file
Important note: install AX 2009 client on each client PC. While installation you'll be asked to state an AOS - state any value. This locally installed AX 2009 client needed as it use several additional assemblies which aren't in GAC.
Finally - how to start AX? Simply run a *.bat file.
Hope I was clear enough and do hope I understood what you were looking for ))
只需输入两条路径:
Just put both paths:
怎么样
C:\Progra~1\Microsoft Dynamics AX\50\Client
how about
C:\Progra~1\Microsoft Dynamics AX\50\Client