When I try to open any of the RMS modules (Store Operations Mgr, for example) iwhich are nstalled on my server I get the following message: "ActiveX component can't create object"
I AM able to open them on both of the other computers networked to that server.
I am not very tech-savvy so I'm reluctant to try anything too technical to fix this, but do any of you have something simple that would work? Or at least something that would help diagnose the problem?
Thanks.
Hi there,
It depends on what version of RMS You have installed... Anyway, there is a solution published on this news group, just search "ActiveX" and You will see the solution... This happens when You install some software after You have installed RMS on the PC...
Regards, A.
I did find a that post and it had link to the MS knowledgebase to fix the issue.; I don't have an RMS contract and it looks like I can't get to that place without one. Any ideas??
Here's the link:
Hi,
I had the same problem 2 days ago on one of the tills, but once I installed IBM upos drivers everything seems to be working fine. ftp://ftp.software.ibm.com/software/retail/poseng/upos/upos195ga.zip That package include ActiveX controller
Regards, Arthur
"PRJ" wrote:
Those drivers are for the IBM 700/500/469x series machines only.
I noticed this after XP SP3 on one of our machines. A repair installation of RMS fixed the problem.
Go to add/remove software in the control panel, find Microsoft Dynamics RMS in the list and select it, click the 'click here for support information', then click the repair button. Have source CD handy.
.Hi, this was posted by one of the users of this newsgroup, Gopher (so all credits for him), I think I remember that this solved the problem @ my client site...
Best regards, Antonijo
"I tried re-installing twice, re-installing xp sp2, system restore, all didn't work. You'll notice that windows update doesn't work either. What fixed problem was running regsv32 MSXML3.DLL, to fix running windows update. Fixed MS RMS error also."
Just thought I would post back with the solution we found for this error. Essentially all we did was run a System Restore to a date prior to when the ActiveX message started showing up. That fixed the problem and I can now open all the modules on that work station. Very simple fix.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.