i can use Server.CreateObject("Scripting.FileSystemObject") successfully, why this excel.application cannot work?is there any other way to read data from an excel file?
I'm using Server.CreateObject(Word.Application) to execute a spell check. Works fine, but we'd like to add a few of our more common company-isms to the dictionary, as they're getting flagged every time.
I tried opening Word on the Server and adding one to the dictionary. I also tried it locally (which didn't make any sense, but still). The word still shows up as an error. Is there a way to customize this dictionary?
In file '1.asp' I call Server.CreateObject("a") to create an instance of object 'a'.
I then call Server.Execute("2.asp") and want to pass the reference to the object 'a' I just created to the script executing in '2.asp'. Session cookies are not enabled so there is no session object.
Does anyone know if there is any documented way of doing that? or if there is a good/right solution to this problem?
My system has a problem when I invoke the fileSystemObject to create a text file (it worked ok long before.) The asp seems running, but actually never finishes. I don't know what I done wrong to the server. How can I fix the problem? Is there a way to resinstall the filesystemobject to the server?
why the second statement below hangs the call to the server. I am running Win2000 , SP4, IIS 5.0 on a local machine. I recently applied SP4 and had to re-install IIS. The code use to work okay under Sp3.
Set TypeLib = Server.CreateObject("Scriptlet.TypeLib") TempGUID = TypeLib.Guid Response.Write TempGUID & Chr(13) & Chr(10) Set TypeLib = Nothing
I have a VB script function that creates an instance of an ActiveX object on the server. The problem is that even if I delete the physical DLL on the server,it still creates the oblect. Which means it's not pointing to the correct DLL. I searched the entire registry and all strings were pointing to the same physical path. But as I say, even if I modify or delete this DLL it's one of our own ActiveX component, it still works.
I also searched the entire server for this DLL's name and found it in a couple of other places. I then renamed those DLLs to ".old". Have you ever heard of anything like it ? Somehow there must be a cached version that the server use when I call the CreateObject method instead of using the registered one.
I've got an asp page using CDONTS for mail. It's running on an NT4 server with the latest updates. I don't have any problems with the page except I want to convert it to a vbscript (.vbs) file so that I can schedule it to run with Task Scheduler. So the original page works fine.I've copied the page code and edited it to scripting standards and saved it as a .vbs file. It's on the same server as the original asp page.But I get this error when it runs: ActiveX component can't create object: 'CDONTS.NewMail'
How do you capture an error when executing "Server.CreateObject" from and asp page. The object does not get created and no error message is reported. I know the application recognizes the existence of the registered dll but it does not creat it
I am new here so hi to all anyone can help me as i have a problem when i create the object Set objWord = createobject("Word.Application") i get the error Microsoft VBScript runtime error '800a01ad'
I'm studying "Visual Basic Developer's Guid to ASP & IIS", and I am following instructions an pp 72-75.I am creating a WebClass, and enter code as instructed, and it all is entered correctly.
When I try and run, I get the folowing error:
"The call to Server.CreateObject failed while checking permissions. Access is denied to this object."
I've not compiled this, but am following instructions to just run the project.Is this not possible without compiling it?
MSXML3.0 is installed on the server.When calling the function below I get an error:
Server.CreateObject("MSXML2.ServerXMLHTTP.3.0")
However when using Server.CreateObject("Microsoft.XMLHTTP") the object gets created just fine.Is there a difference between the 2 functions?Is the second one using MSXML3.0 or an older version? What could be causing the first call to fail?
my problem is my Server.CreateObject("ADODB.Errors") fails with Invalid ProgID. For additional information specific to this message please visit
the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
My other Server.CreateObject's work for other ADODB objects but not for this one. Any ideas why and how to fix? i m using Windows 2000 Server SP3.
I made a small executable file in VB, compiled it and threw it in the Bin folder of my virtual web directory, however when I try to run it from an ASP webpage I keep getting the error that it can not create the object.
After some googling everyone seems to say that you must register the .exe with the server first. My question is, how do I go about registering the .exe file with the server (I have admin access to the server) so that I can use it in my ASP webpage.
I just setup a new machine with Vista Business Edition and IIS 7. I had to turn on IIS 7 attributes including the IIS Manager. Not sure what options I needed I turn them all on that even remotely look like I might need them.
The IIS Manager looks total foreign to me but eventually I figure how to add a virtual folder. I then started making script files in html, javascript and vbscript. I would run them through IIS 7 using the URL: http://localhost/../filename. This all worked fine and I was able to try most of the code that I had used on IIS 6 under XP.
I then start adding ASP server-side calls to the script. I tried several objects: Request, Response..etc. and they worked fine. The problem started when I started using the Server object. In particular when I added the line:
Any idea why this is happening? The directory exists on the FS. It's an upload script to put files in a database directory. It errors out on the upload.
Server object error 'ASP 0177 : 800401f3'
Server.CreateObject Failed
/ProspectTracking/alphatest/default/Upload/upload.asp, line 3
We have a web application that calls a VB dll in one of the asp pages. It works fine on the old NT server but does not display results on the Windows 2003 server (IIS 6?). Does anyone know where I might start trying to find out why this is happening? We copied the web pages and registered the dll on the new server. The call to the dll function returns a string and we just display that string on the next asp page, but it does not show up. Is this some sort of cache issue or ???
When you create an object in classic asp code, should you always use Server.CreateObject("ProgID")? Are there implications with stability (ie memory leaks) if you create COM objects in other ways in IIS?
We use Javascript for our ASP coding, using a mixture of Server.CreateObject() and new ActiveXObject(). The web server hangs occasionally (once every 2-3 months) and we were wondering if this might be the culprit...
I am getting the following error from my ASP application: Microsoft VBScript runtime error '800a0007'
Out of memory: 'Server.CreateObject'
It always (as far as i have observed) occurs when i try to create a new ADODB.connection object in my cCon helper function (opening a connection and returning it):
Function cCon() Dim cnRet set cnRet = server.createobject("ADODB.Connection") 'This is where the error is thrown cnRet.connectionstring = GLB_CONSTR_DB cnRet.open Set cCon = cnRet End Function
The page that errors will typically call this function 6- 10times from different functions which handle their connections in this way: Code: