Announcement

Collapse
No announcement yet.

Unable to load base Error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • msgBldr
    replied
    Sorry, it only seems to happen when I add a new drive. I'll try it if it happens again. NetworkDriveManager reconnects about every ten minutes or so, would seem to take care of it but...

    "When you find that the S: does not connect in script, are you able to browse it with My Computer or Windows Explorer before rebooting?"

    Yes. Not only that, I can run BC3 with that drive with no problems.

    Thanks... Bob

    Leave a comment:


  • Aaron
    replied
    Hello,

    Did you get a chance to try accessing it via \\network\ path and \\ipaddress\ instead of bound Drive Letter s:?

    Drive letter mapping is not as consistent; your particular setup may have a script that triggers and binds the drive letters during boot up (where, a reboot would then help by re-triggering this if the initial binding didn't work.) When you find that the S: does not connect in script, are you able to browse it with My Computer or Windows Explorer before rebooting?

    Leave a comment:


  • msgBldr
    replied
    This only happens when I first create the script. Once it is working it is rock solid.

    There are three drives involved:
    The source drive, local.
    The target drive, network S:
    The script drive, network N:

    Since the script runs but can't complete I'm assuming that the problem is with the target S: drive. This is generally a new drive, recently defined but connected with NDM.

    The session invoked by the script will run just fine outside of the script. The curious thing is: why does rebooting fix it?

    This is not a big deal for me just annoying. It happens just often enough that I can't remember from last time what I did.

    Great product, extremely useful in many ways. THANKS.. Bob

    Leave a comment:


  • Chris
    replied
    Our forum only requires moderation of the first post for new accounts. Your posts shouldn't require moderator approval, so the last post we can see in the forum is the "rebooting to the rescue" post marked 10:43 AM yesterday.

    Leave a comment:


  • msgBldr
    replied
    I thought I replied but it has not shown up. Is there a delay? Moderator?

    Leave a comment:


  • Aaron
    replied
    This error is usually due to the network drive not being available at the time the script is attempted. Failing to load a base folder is a fatal error, and BC3 scripting immediately exists.

    How often does your script run and how often do you run into this error? Are you bound to a drive letter or accessing the network path directly with \\computername\folder? If using the network path, are you using the \\computername\folder or \\ipaddress\folder? Sometimes, the IP Address is a more stable method of connection, as long as it is not changing. Would this be an option for you?

    Leave a comment:


  • msgBldr
    replied
    Once again, rebooting to the rescue. Any suggestions?

    Windows 7
    64 bit
    Network drive
    Connected with NetworkDriveManager

    Leave a comment:


  • msgBldr
    replied
    I'm getting this error again on a new script that was copied from an old one.

    Regardless of the outcome I would really like to see more information when the error occurs. That is, "The system cannot find the drive specified" is pretty vague. Which drive? would be useful.

    Maybe an enhancement request?

    Thanks... Bob

    Leave a comment:


  • msgBldr
    replied
    Reboot fixes this

    Originally posted by pmolaro View Post
    The "Local to Dev" script runs without any issues. However, the "Dev to Production" script always returns this error:
    3/31/2010 2:04:01 AM Fatal Scripting Error: Unable to load base folder
    3/31/2010 2:04:05 AM Script completed in 4.05 seconds
    I was scratching my head over this same error. Just for grins I rebooted and it worked. Go figure.

    Leave a comment:


  • Aaron
    replied
    Hello,

    You can't specify the username and password in script for a network share (although, you can for FTP).

    You can access the drive and save the password outside BC3 for your windows user, or you can use the net use command from the command line in a bat file before running the BC Script from the bat file.

    You can use "net use /?" at the command line for a list of arguments.

    Leave a comment:


  • pmolaro
    replied
    yes, using the share name instead of the drive letter seems to make it better. In almost all of your samples you have the drive letter, so maybe for others a note should be added (unless there is one I missed).

    Also, if i needed to authenticate to one of my drives, how do I do that in the BC3 script? I tried to append one of my paths with: MyPassword /user:xxx\username but that didn't work.

    Leave a comment:


  • Aaron
    replied
    Hello,

    Did you get a chance to test accessing the \\sharename\folder? If you try loading these driver letters or \\sharename\folder locations with the graphical interface, do you also encounter the error?

    Leave a comment:


  • pmolaro
    replied
    @Christoph yes, sorry that was a typo in my post. The actual script has "Y:\" for each block (I just double checked to be sure).

    Leave a comment:


  • chrroe
    replied
    "Y:MySite\wwwroot\assets\Flash\banner"
    Is that a typo? Shouldn't there be a backslash between Y: and MySite?

    Bye
    Christoph

    Leave a comment:


  • pmolaro
    replied
    I have the drives mapped on my local machine to those drive letters mentioned.

    When I say logged in I mean that for each I go to the drive mapping directly (opening My Computer) and I double click the ones I need. The production mapping typically ISN'T logged in so it prompts me for my account info, I supply it and can then browser the drive. The other drives (local and dev) are typically logged in already as I use them often.

    I am running the script via the command line, yes. I made the txt file script then set up a .bat file that I can double click to run the script.

    I will try the drive name instead of letter but I am not sure that will help.

    Leave a comment:

Working...
X