Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to execute command 'Vmenu.exe SUPERVISOR' 1

Status
Not open for further replies.
blocktl

blocktl

Programmer
Joined
Jun 18, 2003
Messages
14
Location
US
I have been working with Exact tech support on this for a week with no solution. Maybe someone else has had this happen.

Pervasive SQL 2000i
Progression 7.6.200 (could be the problem right there)

When I sign in as supervisor and go to visual menu builder, I get the error message "Unable to execute the command: Vmenu32.exe SUPERVISOR".

I have tried reinstalling the client and uninstalling and reinstalling progression, among other things, all to no avail.

Anybody ever see this before and if so what is the solution ?
 
Sort by date Sort by votes
There are no service packs to 7.6.200. Only a few hot fixes.

Blocktl and I are working on this together.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
Upvote 0 Downvote
Try the following and let me know what your results are.

1. Log in to Macola as Supervisor
2. Open a command prompt and navigate to the Macola Root directory.
3. Type in the following command "vmenu32 SUPERVISOR" and press ENTER.

This should open up the Visual Menu Builder application if everything is running properly. Please let me know what the results are, as this may be system/network issue or a Macola application issue.

Thanks,
Scott
 
Upvote 0 Downvote
One addition item to try while you are at it.

If you find that Visual Menu Builder opens sucessfully using the method list above, then try the following:
1. Log in to Macola as the SUPERVISOR user
2. Open a command prompt and navigate to the C:\ prompt.
3. Type in the following command "vmenu32 SUPERVISOR" and press ENTER.

If the method in my previous post works and the second method does not, then I believe that your problem is that the Macola root is not in your PATH environment variable. What ever is the case, please let me know what your results are.

Thanks,
Scott
 
Upvote 0 Downvote
Scott,

I will not be able to test this until Saturday but I will let you know the results. Thanks for the help.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
Upvote 0 Downvote
Scott, those were good ideas, but neither one worked. We got the same error as before. Any more ideas?
 
Upvote 0 Downvote
Sorry for the long delay in a response, but I think that your problem is probably file execution permissions. I would check with the network admin and make sure that they have not restricted the execution of executables in any way. This can be done through the standard network permissions, profiles, or similar (depending on the network OS). A good way to test and make sure, is to log in as a network admin and attempt to execute the program from the command line. If it allows you to execute then you have found your problem, if it does not, try taking ownership of the permissions on the file and changing the permissions on the file itself to allow everyone full permissions.

Give it a try, if I understood your response to mean that when you attempted to execute the program from the command line you received the same error message as when you were in Macola, then I would bet this is the problem in some way shape or form.

Scott Travis
NEXO Systems, Inc.
 
Upvote 0 Downvote
I am experiencing the same problem. When I manually execute from the command prompt, I get a "429 ActiveX component can't create object" error. I have (upon the advice of our consultant) reinstalled the entire 7.6.200 server-side and client-side. This occured after upgrading from 7.5.103f.

maknight
 
Upvote 0 Downvote
Are you running this locally or through Citrix / Ts?

I would check the priviledges on the temp directory on the platform you are attempting to run this under.

Andy Baldwin
 
Upvote 0 Downvote
I'm working on a WinXP Pro system, logged in as Administrator and a User who is a Domain Admin. Neither work. The same happens from any workstation (Win98SE, WinNT, or WinXP).

maknight
 
Upvote 0 Downvote
Have you tried the information below:

Rename the vmenu32.exe in the Macola root directory to vmenu32.old. Then, if you are running P.SQL 2000, rename vmenu32.vb5 to vmenu32.exe. If you are running Progression.SQL, rename vmenu32.vb6 to vmenu32.exe.

Kevin Scheeler
 
Upvote 0 Downvote
TA-DA!! Thanks!! Renaming the files did it. I'm supposing by "Progression.SQL" you meant "Prevasive SQL 7"? I renamed the .VB6 file tole .EXE and it's up.

maknight
 
Upvote 0 Downvote
I can see what you mean. I actually copied it from an infomine from Exact and didn't read it thoroughly. Glad to hear it worked.

Kevin Scheeler
 
Upvote 0 Downvote
Kevin,

I renamed mine as per the infomine and it still doesn't work. In fact I gave up on this. Its only my laptop, but if I ever have to demo VBM for a prospect, I will be in trouble.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
Upvote 0 Downvote
Two things.

If you're like me, you probably change your Macola programs / settings locally to be able to handle different situations.

I would first "remove" Macola from the computer and then reinstall Macola and Flexibility.

To remove it, do the following:

Delete the folder c:\program files\common files\macola shared
Delete the file c:\windows\macola7.ini
Delete the registry key hkey_local_machine\software\macola
Reboot

Secondly, I had worked with another client who was having an issue with some OS's recognizing certain commands like "left" and "right" you'd expect vba to understand. I received some additional things to do with VB6 files locally that might help as well.

The problem is possibly with the VBA Reference. It is not recognizing the regular VBA Functions from these workstations. With previous versions of Flexibility (through 7.5.103), the installer would register components to the server. I am wondering now if these workstations are having issues in locating the correct components. Here is what I would like for you to do:

• Reinstall the Progression Client and VBA Components

1. Using Windows Explorer, go to C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6
2. Delete the folder.
3. Go to C:\Program Files\Common Files\Macola Shared
4. Delete the folder.
5. Go to C:\Windows
6. Delete the Macola7.INI file.
7. Using Start \ Run, run the Progression Client installation (\Macola\Install\Setup.exe)
8. Make sure to restart the workstation after the setup has completed

• Verify that VBA was Reinstalled Properly

1. Using Windows Explorer, go to C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6
2. Make sure that there are 9 files and 1 directory in this folder.
3. If not, go to the following directory:
\Macola75\Install\VBA\pFiles\Common\MSShared\VBA\VBA6
4. Copy all of the files and folders from this directory.
5. Go back to C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6.
6. Paste the files into this directory

• Register the VBA Components

1. Using Windows Explorer, go to C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6
2. Open a Search window
3. Search for REGSVR32.EXE
4. Once located, drag the following files (from the Windows Explorer window) on top of the REGSVR32.EXE file (in the Search Results window) and drop the DLL file:
VBE6.DLL
APC62.DLL

------ or --------
Enter the following command lines into the Start \ Run window:
c:\windows\system\regsvr32 "c:\program files\common files\microsoft shared\vba\vba6\VBE6.DLL"
c:\windows\system\regsvr32 "c:\program files\common files\microsoft shared\vba\vba6\APC62.DLL"

After each, you should receive a message indicating that the registration succeeded.

• Check the Registry for the Path to VBE6.DLL

1. Open Regedit.exe
2. Search for VBE6.DLL within the registry
3. Verify that each entry that has a path to the DLL file has the path of:
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
4. If it does not, change the path within the entry to the correct path.

Hope this helps.

Kevin Scheeler
 
Upvote 0 Downvote
I am getting a different sort of error.

Window Caption: VMB75103F

Window Message: 3709 The connection cannot be used to perform this operation. It is either closed or invalid in this context.

This happens when I launch vmenu32 either from command prompt or from Progression Macola. Please help.

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

X
  • Locked
  • Question Question
Qty_to_ship default to 0
Replies
3
Views
3K
Xannidax
X
mjbasecamp
  • Locked
  • Question Question
Upgrade Progression 7.9.3 to SQL Server 2019?
Replies
0
Views
403
mjbasecamp
mjbasecamp
KOKRSIT
  • Locked
  • Question Question
Macola Progression 7.8.200 | Unable to open anything under AR > Trx > Cash Receipts
Replies
5
Views
530
KOKRSIT
KOKRSIT
HigginsT
  • Locked
  • Question Question
Macola Buying to Stock Ratio
Replies
4
Views
602
HigginsT
HigginsT
prog_0927
  • Locked
  • Question Question
Move Bulk of Orders to Closed Status
Replies
4
Views
652
crystalreporting
crystalreporting

Part and Inventory Search

Sponsor

Back
Top