ActiveXObject Problem - WScript.Shell On Windows 2003 Server
I have installed MSDE on my local computer - Windows 2000 Professional. I have created a function which runs me a link whose path is placed in the input field. This function looks like this: Code:
I'm using this code var file = new ActiveXObject("WScript.Shell"); file.Run(FileName);
but in case the file name is of type html i get the file in the same window and i'm 'loosing' my site.i want to have the new opened document in a new window.
im using server object Wscript.Shell in an asp page to run a bat file, under C:inetpubwwwroot, and after i run the ASP page, it give me an error message that
Error Type: Microsoft VBScript runtime (0x800A0046) Permission denied /wss1/bat.asp, line 22
im sure that Windows Scripting Host is running well in my pc. But it still giving me this problem.below is my coding of the asp pages. Code:
I made some of the web pages using ASP on windows 2000 server, now i wanto to upgrade my Operating system from windows 2000 server to Windows 2003 Server , Are my web pages will work fine if i do this upgradation or there are any configurations on IIS i have to make to work fine ....
I've had a new server installed for me. with Windows 2003 and II6 with ASP.NET. but I want to run a small (but important) application written in ASP(all .ASP files)
as it stands the server will not 'understand' .ASP files (only .ASPx)To avoid having to modify the whole application ( :-} ) can I get the server to execute. ASP files?(is it as simple as copying over an existing II4 ASP.DLL and installing that?
We have several extensive sites and all use a lot of include files. We have the coded as include file and virtual include using ../ since it is a shared server etc. The sites were moved by the hosting company to a new windows 2003 server and now we get invalid path error part of the time, others it works fine.
The host says it is our programmers did not follow asp procedures and used ../ I always thought this was ok, it was never an issue before the move...is this new to windows 2003.
I just set up an acct. with godaddy for a shared virtual dedicated server using Windows 2003 and IIS 6. None of my ASP scripts work to send emails using CDONTS. Research took me to how to install the cdonts.dll file and after doing so I don't get the error about not being able to create an ojbect but rather that of permissions on the line that has the .send. Other research led to me believe that windows 2003 does not support cdonts at all? I'd prefer to use CDO but I was told by Godaddy that the script below is not supported on a shared server - Code:
Some one has posted this question on 10th August, as CDONTS is not working on windows 2003 serever. I have the same problem and I copied CDONTS.DLL from Windows 2000 Server and registered on Win 2003 server but it giving the error on line when I calling method send of the object.
Error is Microsoft VBScript runtime error '800a0046'
Permission denied
I tried to register CDONTS as COM+ with Admin user right to execute but it still giving same error.
if I can use CDONTS in W 2003 Server environment to send emails the same way it is used in W2K Server. I have heard that CDONTS is no longer available in W 2003 Server and if so, how can I send emails from ASP page.
I have a site thats been up for 2-3 years on an NT4 server using IIS & Ms Access, and I used MAcromedia Ultradev to build it with MX 2004 to maintain it.
The hosting company decided to upgrade the server to Windows Server 2003 and now none of the Dtabase connections or include files can be found. Does anyone know what I need to do to re-code this site.
Currently, I move a application from win 2000 server to 2003 server, I use some vbs file in this application, however, it seems that those vbs file can not be run from 2003 server. Below is my code, can some one point out what did I do wrong here?
DIm objShell Set objShell = Server.CreateObject("WScript.Shell") objShell.Run(ExeName) Set objShell = Nothing
I am recieving a weird error when I try to run asp scripts on my local machine, I can use pages that access a database, but when I try to write to the file system ie upload a file I get the error message below.
Hi people, I currently have a website and the asp pages include the following line:
"Set Tools = Server.CreateObject("MSWC.Tools")"
My site is hosted on Windows 2000 server.
The hosting company has offered me a new deal but on Windows 2003 servers, I took them up on this but found that my asp pages did not function as these servers do not have the Internet Information Server (IIS) Resource Kit installed on them. I found this out by looking at http://support.microsoft.com/kb/q249290/.
As I am not the original creator of the asp pages and have no knowledge of asp, can anyone help me fix this problem where my asp pages will function correctly on the Windows 2003 server?
I am currently in the process of converting a website from an existing web host to our servers. This website used the WScript.Shell command to execute a series of Java commands that would send an encrypted email.
I ran these commands directly on the server and they execute properly, but when I try to run them from within the WScript.Shell command then I get a return code of 1, and the actions that should be completed are not.
The shell is executing a .bat file which is in the same directory the text files it needs to run the following sample command(s): Code:
I am trying to run a command line from an ASP page. I am using windows 2003 with IIS6. I am able to get this to run on my local machine (Windows XP IIS5). Here is my code:
For win2k adv server/iis5.0 trying to run an external program from my asp routine that has multiple parameters, see following.
set shell = server.createobject("wscript.shell") shell.Run """f:phsDatahtmldochtmldoc.exe"" --webpage -f phsnew.pdf phsnew.htm"
program either doesn't get invoked, or has an error, but since it has no error log i can't check that, so not sure why not getting a result i have run the program successfully from the command line in that directory, so know it can be run in the first place and the asp program creates and writes files in the same directory so i don't think its a permission problem. asp doesn't complain with any errors.
I am trying to use the Run method of WScript.Shell to run a program that creates image files on the server. When I run the program through the command line it creates a text file and a bmp file which is what it is supposed to do.
If I run it from an asp page it doesnt do anything, it also doesnt give me any error messages. I can run the same vbscript code in a standalone vbs file on the server and it works right. Code:
I've been testing the WScript.Shell object and the Run command now for a server query. The file I am running generates a file with the server querys which i later on parse in my page. But there is a problem. When running the Run command om my Windows XP machine it all seems fine. But when trying to run it on my webserver (not configured by myself) I get an error, or the command fails. It's nothing wrong with the acctuall command but ASP seems to not want to allow the Run command.
First I though it had to do with user privilegies but after giving the IUSR_X full access it didn't help. So, does anybody know a solution for this? Exactly what do I have to configure, for what user, to make this work on my webserver (win2k).
Trying to view asp page which has the following code in Set obj = WScript.CreateObject('WScript.Shell')
It falls over on this line saying 'Activex cannot create component (wscript.shell)'. Doing the same in a .vbs file results in the same error. The platform is NT4 Server Service Pack 6a.
I've made an ASP page that calls a small executable and collects its text output into a variable ("strExeOut") below. Below is some code similar to the one I use for that purpose.
strExe = "C:whatevermyprogram.exe -h1 -d33"
Set objShell = CreateObject("WScript.Shell") Set objScriptExec = objShell.Exec(strExe) strExeOut = objScriptExec.StdOut.ReadAll
I developed this in my own computer and the whole thing works like a charm, but unfortunately I assumed my hosting provider would let me run the (little and harmless) exe, and they won't.
Therefore I have to run only the "exe" portion of the code in another web server and send back the output to my website on the net. I'd like to get some feedback on what would be the best way to call an exe on another server, and to have the output sent back.
im trying to run a bat file on windows server 2003 and am running into nothing but problems.
i have IIS on my XP workstation that accesses the 2003 server. what im about to explain below works properly on the XP IIs.
i have two files: somefile.asp and somefile.bat. the asp file creates a wscript.shell and then tries to execute the run method for somefile.bat.
however, it isnt working. after an unexaggerated 7 hours of searching google/etc, i have found nothing but frustration and deep, seething anger regarding this problem. Code:
I have a big problem with some part of my code, where I'm using the wscript.shell method to open a file...
I've tried this:
dim shell set shell= createobject("wscript.shell") shell.run "C:Clip_CreatorTVSA02.bat" set shell=nothing
and this
Function fnShellExecuteVB() dim objShell set objShell = CreateObject("Shell.Application") objShell.ShellExecute "C:WINNT otepad.exe", "", "", "open",1 set objShell = nothing End Function
I don't get any error but the application doesn't starts, I've also tried executing the notepad.exe and occurrs the same, nothing happens, I don't get error but the notepad doesnt lunch...
I'm getting tired about this code, I've tried a lot of kinds of scripts but I got the same result...
I have a process that creates a whole bunch of files in a specified directory. The names of the files are the employee IDs with an .txt extension, so they are like
EMP001.txt EMP002.txt EMP003.txt
The background is a bit more complicated so I won't bore you with it, but I hope that I can add a button on the asp page that would
1) go to that specified directory, which is database-driven by the department id, such as
D:DepartmentDEPT001
and I'll be able to figure the directory path from the existing code
2) then loop through each employee id and append the employee name, so the above will become
The employee names are also database driven and my asp page will be able to provide the information.
What I would like is to have a button that would open the cmd.exe and make the appropriate changes, and then do the rename, and then close the cmd window.
dim oShell set oShell=WScript.CreateObject("WScript.shell") oShell.run ("C:WINNTsystem32cmd.exe /c C:WINNTsystem32 otepad.exe") set oShell=nothing
works as expected in the context of a .vbs script and doesn't work (with the following changes made...) when inserted in a .asp web page under IIS ?
dim oShell set oShell=Server.CreateObject("WScript.Shell") ' intReturn = oShell.run ("C:WINNTsystem32cmd.exe /c C:WINNTsystem32 otepad.exe") response.write(intReturn) set oShell=nothing
the Shell object is well created (i can check some of its properties) but the oShell.run command doesn't seem to execute the given command line.
I need to use nslookup on an asp page. So I use the sort of code I can see in the discussion group:
SET objShell = Server.CreateObject("Wscript.Shell") DIM objExec SET objExec = objShell.Exec("%comspec% /c nslookup -type=MX "&host)
but I get "access denied" on the SET statement. (It doesn't matter what command I am using in the shell.)
On the physical IIS application directory Web sharing is enabled I enable anonymous access I have full control for the internet guest account. I have permission for scripts and executables on the virtual directory application protection low read write directory browse
I have enabled web sharing for windowsSystem32. (I probably shouldn't have!)
Clearly there is something I have forgotten. But what?
I can run these commands successfully from the command-prompt on the server but from an ASP page, I get nothing not even an error. The Text output for NET PRINT is a blank text file.
I feel something is different on the permissions side because this code/approach use to work fine.