Office 2003 activated, but can "CreateObject"

[Jordan]

I put a computer on the network about a month or two ago and installed
Office Basic 2003. I deployed an Access 2003 runtime and my app just like I
did on 50 other computers using Windows Group Policies to deploy so all
computers should be the same.

Now on just this one computer when I run the code below which starts Excel,
creates a new workbook, etc. I get a message telling me that I cannot use
that feature because it expired. Also, a program create by one of the
engineering team that uses LabView to program is experiencing the same
problem trying to do a similar process via an ActiveX control.

Because this computer has been on the network only a couple of month and the
message is about expiration I naturally assume that there is an issue with
the MS Office Activation process, but when I go to Word, Excel, or Outlook
to activate it tells me that it is already activated - as I already know.


Dim objXL As Object
Dim strWhat As String, boolXL As Boolean
Dim objActiveWkb As Object

Set objXL = CreateObject("Excel.Application")
objXL.Application.Visible = True

objXL.Application.Workbooks.Add
Set objActiveWkb = objXL.Application.ActiveWorkbook
objActiveWkb.Application.ActiveSheet.Paste
objActiveWkb.Application.ActiveSheet.Cells.EntireColumn.AutoFit

 

['69 Camaro]

Hi, Jordan.

Now on just this one computer when I run the code below which starts Excel,
creates a new workbook, etc. I get a message telling me that I cannot use
that feature because it expired. Also, a program create by one of the
engineering team that uses LabView to program is experiencing the same problem
trying to do a similar process via an ActiveX control.

Is it possible that a 60-day trial version of Microsoft Office was ever
installed on this computer? Uninstalling doesn't always remove all Registry
keys.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.

 

[Jordan]

Not possible. The installation has been pushed down to all computer using
the same source. This particular computer was one of a dozen+ setup the
same way using Windows Server's Remote Installation Service to install
Windows XP and Windows Group Policies feature to install Office 2003.

The only way I could see the 60-day trial being installed is if I
inadvertently put in a 60 day trial code instead of the one on the OEM disk.
I this cannot be the case because I can start any office app fine and use it
without issue. It is just when I programatically try to start a new
document (Excel and Word). It happens when I do it from VBA and from other
programming sources like LabView.

Thee only thing unique about this computer is that a Software Developer uses
it. Of course I asked them if they installed anything or if they messed
with the setup in any way and they assured me the did not and there is no
possibly way their software could mess up anything because everything they
write is bug free. Scout's honor.....

 

['69 Camaro]

Hi, Jordan.

The only way I could see the 60-day trial being installed is if I
inadvertently put in a 60 day trial code instead of the one on the OEM disk.

That would be incredibly difficult to guess a 60-day trial product key that
actually activated the product. Or did you have a 60-day trial product key
handy at the time?

I this cannot be the case because I can start any office app fine and use it
without issue. It is just when I programatically try to start a new document
(Excel and Word).

It can happen, but only if more than one version of Office is installed. If the
last version installed were a 60-day license that has expired, programmatically
opening the application would give you the error message from the last version
installed, yet opening the application from the Start Menu or a shortcut that
specifically names the path to an unexpired version would make everything look
peachy keen. Hence, two different outcomes from what appears to be the same
application opening.

Thee only thing unique about this computer is that a Software Developer uses
it.

That could be the problem. ;-)

More likely, the installation partially failed or some new application was
installed on the computer afterwards that trashed part of the Office
installation. You can try re-registering the Automation files, but check the KB
article on the following Web page first for some troubleshooting tips:

http://support.microsoft.com/kb/q244264/

If that doesn't help, re-register these files (located in C:\Windows\System32):

Asyncfilt.dll
Oleaut32.dll
Olepro32.dll
Stdole2.tlb
Stole32.tlb

Click Windows Start, and then click Run. Use the following command:

Regsvr32.EXE "C:\Windows\System32\Asyncfilt.dll"

.. . . and so on for the other files.

If that doesn't work, uninstall and reinstall the Office applications.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.