VB Script not working

Since this thread is similar to what I want to ask Im writing it about the problem that I have:
In windows xp and 7 I did not have this problem but on WINDOWS 8 is a real headache, Right now I have like 20 scripts that use access 2003 that connect to SQL Data in a server, but the first problem is that I cannot map drives classic style like Z:\ or H:\ etc
here is one simple example of the script


Set objShell = CreateObject("WScript.Shell")
Dim accessApp
set accessApp = CreateObject("Access.Application")

accessApp.Visible = "True"
accessApp.OpenCurrentDatabase "Z:\Contabilidad\Autorun\Reportes\CHEQUEOSAB.mdb"
accessApp.Run "ActualizaDatos"
accessApp.CloseCurrentDatabase
accessApp.Quit

Set objshell = nothing
set accessApp = nothing

And the drives are mapped, and connected when trying to run the script?

Are you using Homegroup for Networking or regular MS Networking? I don't know if that would matter, Windows 7 has Homegroup too.

I found these articles:

Task scheduled vbscript cannot access mapped drive when run on logged off remote computer

Access network share from within VBScript eg FileSystemObject - Stack Overflow

XweAponX said:

And the drives are mapped, and connected when trying to run the script?

Are you using Homegroup for Networking or regular MS Networking? I don't know if that would matter, Windows 7 has Homegroup too.

I found these articles:

Task scheduled vbscript cannot access mapped drive when run on logged off remote computer

Access network share from within VBScript eg FileSystemObject - Stack Overflow

Click to expand...

Actually ; i have a windows 8, upgraded to 8.1, I even have a simple script "open notepad" that with a double click from the mouse works perfect , but if I programmed it to run in taskschd.msc it shows the state running but it doesnt show anything on screen

WHY DOESN'T THE TASKSCHD.MSC WORK ON WINDOWS 8.1 IT SEEMS AS IT IS BUT IT DOESN'T DO ANYTHING FOR EXAMPLE I HAVE A VBS PROGRAM THAT OPENS NOTE PAD, IF i DOUBLE CLICK IT , IT OPENS NOTEPAD , BUT IF I PUT IT TO RUN AT A CERTAIN TIME IT DOESN'T ON TASKSCHD.MSC, I MAY DOING SOMETHING WRONG OR IS THIS A BUG BECAUSE ON WINDOWS XP WORKS PERFECTLY OR DOES IT HAVE TODO WITH THE SCRIPT ON VBS TO RUN ON WINDOWS 8.1

You mean, NO scheduled tasks run?

If the script ruins, it's a problem with maybe how the task was created.

Make another scheduled task, like to open a simple program? See if it opens at the allotted time.

Sounds like you know what you are doing with the Scripts, the problem is getting task scheduler to run it.

XweAponX said:

You mean, NO scheduled tasks run?

If the script ruins, it's a problem with maybe how the task was created.

Make another scheduled task, like to open a simple program? See if it opens at the allotted time.

Sounds like you know what you are doing with the Scripts, the problem is getting task scheduler to run it.

Click to expand...

I already did one as simple as it can be, just to open notepad.exe locally and it works perfectly on the desktop with a double click from the mouse, but if I put on taskschd.msc doesn't show anything , i don't know if it is a bug on the system win8.1 but it's killing me!!!

Well, for one thing, when you schedule a task, it normally runs hidden.

You can look at the task, and it should tell you if it ran at the time it was meant to. I have wanted to check my "History", to see if my scheduled tasks have run, but the "History" for Task Scheduler is by default blocked.

I have several programs that run scripts, and they are all running daily, I can check the status of some things, and it shows that the script had run.

Is there any way to create a task that will change something in a file or a program, that you can open up later and see if the changes were applied?

Also if a task did not run properly, it will give you an error status, so you should put t=your desired script in there, tell it to run at a certain time, then go in there about 10 minutes after the time it was scheduled, if it failed, it will say so.



As you can see, it shows me when the tasks will run next, and the last status. Stick your script in there, and tell it to run in 15 minutes, then check the status in 20 minutes. It will probably open Notepad, but hidden. I take it your script, I think it was, pulled up an email program and attach a document to it? Just check it and see if it had worked I guess.

that's exactly what the other scripts are supposed to do, for example I have this:
I have many of them that open an ACCESS database to pull info from SQL and update all the info, and I already check th e file and doesn't show any changes , whe nto check the history of the task but only shows 5 items, but none saying that there was a problem, and trying not to give up on win8.1, but with this problem it's really hard not to give up

Well then it has to do with being able to affect changes across the MS network, but you say the script works when run manually? Arg!

If this is something that is needed, I'd go back to what works, until a solution is forthcoming in Windows 8.1.

You say it works in Windows 8? You will have to weigh the advantages of using 8.1 over what works with 8. If too many things in 8.1 don't work the same way as they did in 8 then it's not worth it.

Each time a new OS comes out, I have about 50 to 100 programs and other things I have to make sure all work right. If they don't work, I don't update.

XweAponX said:

Well then it has to do with being able to affect changes across the MS network, but you say the script works when run manually? Arg!

If this is something that is needed, I'd go back to what works, until a solution is forthcoming in Windows 8.1.

You say it works in Windows 8? You will have to weigh the advantages of using 8.1 over what works with 8. If too many things in 8.1 don't work the same way as they did in 8 then it's not worth it.

Each time a new OS comes out, I have about 50 to 100 programs and other things I have to make sure all work right. If they don't work, I don't update.

Click to expand...

only on Windows xp pro, i dont have a windows 7 pc so i cannot tell that it works there too!!!!

But it worked on 8? If it did, stick with that.

XweAponX said:

But it worked on 8? If it did, stick with that.

Click to expand...

sorry, but it didn't that why I thought that if I upgraded it to 8.1 it would work but it is the same problem... thank for your time

Ok, so it's XP then. Damn, I guess the Script was made for an older version of Office, and on XP, so the conventions used are specific for XP and Office 97.

See, this is why Hospitals are still using XP. Crap, crap crap.

Have you tried re-creating the script on Office 2010 or 2013? It can be done, but there are a lot more protections on it. It's because it has been abused by hackers.

Windows Vista through 8 use different Naming Conventions than XP, which uses the old Universal Naming Conventions:

UNC Path Names in Windows - Universal Naming Convention

Maybe you can disable it in Windows 8, see if the scripts work:

WD97: How to Disable the Use of Universal Naming Convention (UNC)

I've had to do this with a Networked Program, that installs over a MS network. It will not install when UNC is enabled, so I had to shut it off, and the problem I had was with 64 bit OSes, the 32 bit versions of Windows 7 allowed the program to go right in, but on 64 bit 7, it told me to disable UNC. So I used the instructions from that link.

I suppose you are using a 64 bit version of Windows 8, try shutting off UNC, then see if the scripts work. It has something to do with the mapped resource wanting to use the command processor.

XweAponX said:

Ok, so it's XP then. Damn, I guess the Script was made for an older version of Office, and on XP, so the conventions used are specific for XP and Office 97.

See, this is why Hospitals are still using XP. Crap, crap crap.

Have you tried re-creating the script on Office 2010 or 2013? It can be done, but there are a lot more protections on it. It's because it has been abused by hackers.

Windows Vista through 8 use different Naming Conventions than XP, which uses the old Universal Naming Conventions:

UNC Path Names in Windows - Universal Naming Convention

Maybe you can disable it in Windows 8, see if the scripts work:

WD97: How to Disable the Use of Universal Naming Convention (UNC)

I've had to do this with a Networked Program, that installs over a MS network. It will not install when UNC is enabled, so I had to shut it off, and the problem I had was with 64 bit OSes, the 32 bit versions of Windows 7 allowed the program to go right in, but on 64 bit 7, it told me to disable UNC. So I used the instructions from that link.

I suppose you are using a 64 bit version of Windows 8, try shutting off UNC, then see if the scripts work. It has something to do with the mapped resource wanting to use the command processor.

Click to expand...

I'll try this and I let you know thanks for your help

Well, I realized you are trying to run a command over the network, Network is great for moving files back and forth, but you have to have a different deal for invoking a command from a network machine.

Windows XP, Vista and 7 have some extra networking protocols that can be installed to help with this, including NetBui, which is what I used in XP for running the executables, but they are all missing from Windows 8.

So since the Protocols can't be installed to 8, next best thing would be to shut off UNC.

I'll look for Netbui for Windows 8 and see if I can get it from somewhere, there is another one, NetBios I think. I cant remember what it was called, but in XP I always had to install them to get my program to work, it told me in the manual for the program. Actually they are not there in Windows 7 either, but I remember being able to get them in somehow.

XweAponX said:

Well, I realized you are trying to run a command over the network, Network is great for moving files back and forth, but you have to have a different deal for invoking a command from a network machine.

Windows XP, Vista and 7 have some extra networking protocols that can be installed to help with this, including NetBui, which is what I used in XP for running the executables, but they are all missing from Windows 8.

So since the Protocols can't be installed to 8, next best thing would be to shut off UNC.

I'll look for Netbui for Windows 8 and see if I can get it from somewhere, there is another one, NetBios I think. I cant remember what it was called, but in XP I always had to install them to get my program to work, it told me in the manual for the program. Actually they are not there in Windows 7 either, but I remember being able to get them in somehow.

Click to expand...

thank you for your time , I appreciated

I just checked, seems that you CANNOT install NetBUI into Windows 7 or 8. But one guy found a way to do it:

How do you install NetBEUI protocol in Windows 7? - Microsoft Community

If you are running a 32 bit version of Windows 8 or 8.1, you can use his workaround.

That might be another issue, if you are using a 64 bit version of Windows 7, 8, 8.1 - I install 32 bit systems to offices, exclusively - If one of my clients buys a computer with a 64 bit OS, it becomes 32 bit in short order.

64 bit is freakin great for playing games, unfortunately some people need to do WORK.

If you can't get NetBui installed, then try IPX/SPX:

IPX on Windows 7

This script runs MS Access on the local computer and commands Access to open a database file located on a network drive on the remote computer. Nothing is executing remotely. Just like running notepad locally opening a text file on the Z: drive. So I don't think you need additional network protocols. All you need to do is map the drives and run the script, post any errors received. My feeling is that how you map the drives or the scripts themselves might need minor changes. It should work.

That's how most of the scripts work. However, in the one program I use that does just that - Access a remote Access database - it absolutely will not work unless NetBeui is installed or Universal Naming Convention is disabled.

Mostly it affects 64 bit workstations, and this was the first time I ever saw the "UNC must be disabled" error, it was on a 64 bit machine. Once I disabled it, I was able to pull up the remote database.

The program is based on an Access 97 database file, the newest ones might upgrade the database file to Access 2000, nothing higher than that, otherwise the program will not work. This is a program being used NOW, by hundreds of thousands of shops all over the world, probably even more. And because it is based on an Access 2000 MDB file, a PROTECTED MDB file, it absolutely requires UNC to be disabled, or, to be installed to Windows XP so that NetBeui can be used.

This is why I always say, if you are buying a computer for a Business, DO NOT buy it from a store, contact Dell Business Services, they'll make you a system that's 32 bit, that way it can be set up for a business environment.

If there comes a point in the future where 32 bit OS's are no longer distributed, then this program will no longer be able to be used, and when that happens, it will affect every person in these forums, at least who have cars, because every person who drives must bring their car to a shop occasionally, this is the database program used by just about every shop in the world.