Geopak Drainage - Drainage VBAs-Drainage Stub-Out Report

I am getting the following error when trying to run the VBA - Drainage Stub-Out Report from the FDOT menu.

I have the Geopak project manager open to the current project as well as the Geopak Drainage project open. I have an active network set. Once I select OK I receive this dialog box

I pick the browse icon and then get this dialog box\error

I have looked on the Microsoft side to see if there is some bogus add-in or startup form for Word and Excel and found nothing. I also repaired Office 2010. Any help would be appreciated.

FDOTSS4

MSV8i SS3 - 08.11.09.714

Geopak SS4 - 08.11.09.845

Top Replies

Offline Bob Thorburn Wed, Feb 5 2020 8:49 AM in reply to Sean Keene +1 verified

Sean, It's not likely that it's the same issue as it was 5 years ago, unless the user is still using Windows XP. Send me the users contact info and i will takke a look at the problem. Robert.thorburn…

Parents

0 Offline Christiana Holmes Tue, Sep 22 2015 8:46 AM

I replied to your email with steps to follow. If you are still having issues please let me know.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Zachary Billings Tue, Sep 22 2015 12:20 PM in reply to Christiana Holmes
What was the solution to this issue? I was figuring it was running the geopakcom.exe as Administrator. File located here: C:\Program Files (x86)\Bentley\GEOPAK\GEOPAK (SELECTseries 4)\bin

Then if you go back to an SS2 project, you just do the same thing, but in the V8.11\bin folder.

Zachary Billings, P.E.

Senior Roadway Engineer (Licensed in FL and MI)

CONSOR Engineers, LLC

System Info:

Windows 11 | Intel Core i7-13700k | Nvidia RTX 4090 FE | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME

ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00

YouTube Page for ORD: https://tinyurl.com/BillingsCADD
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Offline Zachary Billings Tue, Sep 22 2015 12:20 PM in reply to Christiana Holmes
What was the solution to this issue? I was figuring it was running the geopakcom.exe as Administrator. File located here: C:\Program Files (x86)\Bentley\GEOPAK\GEOPAK (SELECTseries 4)\bin

Then if you go back to an SS2 project, you just do the same thing, but in the V8.11\bin folder.

Zachary Billings, P.E.

Senior Roadway Engineer (Licensed in FL and MI)

CONSOR Engineers, LLC

System Info:

Windows 11 | Intel Core i7-13700k | Nvidia RTX 4090 FE | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME

ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00

YouTube Page for ORD: https://tinyurl.com/BillingsCADD
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 Offline Christiana Holmes Tue, Sep 22 2015 12:34 PM in reply to Zachary Billings

Sometimes that will work but lately we are having some issues with some of the Windows .OCX files that the Drainage VBAs are calling not being registered or being out of date. If you are having this issue as well I can help walk you through the solution.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Sean Keene Thu, Sep 24 2015 8:59 AM in reply to Christiana Holmes
The steps that Christina had me go thru did fix the issue. It is related to the Windows.OCX files either out of date or not registered. Christina sent me 2 OCX files and I registered them.
Answer Verified By: Sean Keene
Cancel
Vote Up 0 Vote Down

Sign in to reply

Reject Answer

Cancel
0 Offline Sean Keene Mon, Feb 3 2020 8:18 PM in reply to Christiana Holmes
Christiana,

I realize this is an old post but I was wondering if you could send me the OCX files from the issue I was having previously? I have one machine that will not produce the stubout report and I cannot find the OCX files you sent me previously. I want to check to see if the machine has the correct OCX files and if they are registered.

Thanks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
+1 Offline Bob Thorburn Wed, Feb 5 2020 8:49 AM in reply to Sean Keene
Sean,

It's not likely that it's the same issue as it was 5 years ago, unless the user is still using Windows XP. Send me the users contact info and i will takke a look at the problem.

Robert.thorburn@dot.state.fl.us
Answer Verified By: Bob Thorburn
Cancel
Vote Up +1 Vote Down

Sign in to reply

Reject Answer

Cancel