Pages

Search

Office 2003 Error 1911 wisptis.exe - Microsoft Office forums

Office 2003 Error 1911 wisptis.exe - Microsoft Office forums

Office 2003 Error 1911 wisptis.exe

Posted: 06 Dec 2004 12:33 PM PST

Problem persists if CD is copied to hd. I assume it's no big deal since
pressing the 'ignore' button when the error message comes up does not appear
to interrupt the repair proces. Nevertheless, I just wondered what causes
this error. (I've seen the discussions on the alleged redundancy of
wisptis.exe)
Thanks anyhow - Richard

"Roady [MVP]" wrote:
 

I would like to download Microsoft office in full

Posted: 05 Dec 2004 09:45 PM PST

"E.JAY" <microsoft.com> wrote in message
news:com... 

I think the only download sites available would be WAREZ sites, or the MS
Developer Network.

The WAREZ sites would probably prove to be detrimental to your PCs health
and the Developer Network requires that you employ several developers and a
$2500 application fee, last time I checked.

Office 2003 Upgrade New Install Yields 1608

Posted: 05 Dec 2004 08:21 AM PST

Thanks for the reply, but I had already read the article. None are the
causes are true in my case and the resolution is nothing more a very very
long description of putting in a CD. That much I already knew.
What I really need is information on what the installer is looking for,
because I have provided what I believe (and Microsofts documentation states)
should be necessary and installer still generates the 1608 error.
Does anyone in Microsoft have any clue what generates a 1608 error besides
"Setup could not locate a version...". I already know Setup could not locate
a version.., but a version was provided, so we need to get a more detailed
explanation as to what causes this problem.
Any help that can be provided would be appreciated.

"garfield-n-odie" wrote:
 

How do I uninstall previous version of Outlook?

Posted: 04 Dec 2004 07:51 PM PST

Go to Control Panel>Add Remove Programs, and click on Office 2000, and then
click change (not remove) You can then follow the steps to remove a single
app (that is, Outlook). As posted in reply here, you must use the same
version of Word as Outlook if you use Word as an email editor.

Just a thought, you might try to install Office 2003 SBA complete in a
separate installation (choose custom installation and then install to a new
folder) and give the whole suite a try. For me it's much quicker, more
safe, and has a better "look and feel". Of course you may not agree but as
long as you have it why not try it! You would of course still have to
follow the rule of having only one version of Outlook installed, so you
would still have to uninstall OL 2000.

kip



"hafsusa" <microsoft.com> wrote in message
news:com... 

Office 97 Pro installation problem on Windows XP Pro (with SP2)

Posted: 03 Dec 2004 09:01 PM PST

Hi, John. If you get a "Htmlmarq.ocx was unable to register itself in the
system registry" error message when you try to install Office 97, you can
avoid this error by performing a custom installation in which you deselect
Web Page Authoring
(HTML) in the Office 97 setup options.

"Kodesh John" wrote:
 

Cannot open office 2000 Pro docs once I install Office 2003 Pro

Posted: 03 Dec 2004 11:19 AM PST

With Word closed, search your hard drive for the OFFICEAV.DLL file. Include
hidden and system files and folders in your search. When you find it, note
the folder where the file is located. Click on Start | Run. In the "Open"
dialog box, type the following command (including quotes):

Regsvr32 -U "C:\<path>\OfficeAV.dll"

Replace <path> with the directory path for your OfficeAV.dll file. Click on
OK. You only have to run this command once (not every time you restart your
computer). You should get the message: "DllUnregisterServer in
C:\<path>\OfficeAV.dll succeeded." Your Office 2000 files should open
properly now.


"Jav BTB" wrote:
 

Office MST file hell

Posted: 02 Dec 2004 09:00 PM PST

It works, no idea what i was typing in wrong yesterday but thanks alot.

"Roady [MVP]" <_SPAM_net> wrote in
message news:phx.gbl... 

Deploying office 2003 after deploying MSOCACHE

Posted: 02 Dec 2004 10:49 AM PST

3010, means that the install needs a reboot to complete, these are all MSI
error codes which can be found on the MS website

Regards
Tim

"postalias" wrote:
 

Clip-ORganizer error

Posted: 02 Dec 2004 09:25 AM PST

Try updating your MDAC as described in
http://support.microsoft.com/?kbid=302375 "Clip2002: Error Message:
'Error in the .dll...' or 'Clip Organizer Cannot Complete the
Operation...'". The newest MDAC is version 2.8.

Hartmut Berghoff wrote: 

Entourage 2004 (Mac)-Can't stop messages going to "Sent Items" fol

Posted: 02 Dec 2004 08:27 AM PST



"Bob Buckland ?:-)" wrote:
 

Thanks, Bob. I didn't know about the newsgroups. In fact, there is a
solution there.

To save others the trouble of searching:

use Tools -> Schedules to create a new schedule item. The item is to move
things from "Sent " to "Deleted". As part of the schedule, you can also say
to move only items older than x days or move them every time you Quit or
Start entourage.

Thanks for the pointer!

Roger

Office 2003 Deploy-Makes no sense or by design??

Posted: 01 Dec 2004 07:47 PM PST

Hi Fletch,

This one is a long one, sorry :)

You do not need that long setup command line.
If you place your mst file in the same dir of the msi file (Which is the
recomended way), simply change the setup.ini/setuppro.ini file. The file
resides in ..\FILES\SETUP

In there locate the [MST] section and change the name of the mst file name
to match yours.

Simply running setup.exe without anything else will do.
It automatically calls setup.ini to read the install instructions.

You may have problems then, that are related to relative paths of the
install files so here is what i usually do:

It goes without saying that this will work only with Enterprise/Volume
license media and CDkey...

Server Side:
-----------------
On a file server you normally use, that might be already mapped to users,
make sure this is your directory structure (example):
D:\Apps\Office\Office2003\ <- in here lies the admin point.
Both MSI and MST should be in it. This structure is needed mainly
for security reason.

D:\Apps should be shared, and then mapped as a drive, say P:
so users will see this:
P:\office\office2003

Using a mapped drive is better in this case, as any MSI install records the
original location from where is was installed and then looks for that
location in cases where a reinstall is requested or it needs install source
to fix itself.
Thus if at a later point the original file server that hosted the admin
point is not available, all you need to do is to copy the entire admin point
to another server and simply map the same drive letter to the new server.

If the installation isnt done from a mapped drive, then the user will have
to direct to the new install point (that might be an issue) or youll need a
script to add/change the source location in the registry for each station.

With correct planning you can even overcome this one, In the MST file you
can add install locations, so you can add P:\Office\Office2003 and also
\\Server\Apps\Office\Office2003 thus giving Office better resiliency in
finding the paths and you can even enhance that by creating 2 admin points on
2 servers, and add both locations in the MST file, as long as you remember
the paths should be the ones the end user will see from his station. This is
usually the scenario with big companies that have dispersed file servers and
want the minimize bandwidth consumption by directing users to the closest
file server (using Windows DFS also helps in this case).

In your MST file, make sure you added the NOUSERNAME=True property.

You can also use this property on the command line, so youll not have to
create 2 identical MST files, one for Ghosting an Image and one for normal
use (If you have stations you only want Office 2003 installed on their
existing OS).

More info:
http://www.microsoft.com/office/ork/2003/two/ch5/DepC05.htm

Last thing, edit the setup.ini to include full paths, both uder the MSI
and the MST sections. Use the drive letter for this.


Pre-Ghosted station side:
-------------------------------
Make sure the Drive P: is mapped

Run setup.exe -> P:\Office\Office2003\Setup.exe
You can also add the NOUSERNAME property as discussed above.
(use the newer version of enterprise setup.exe)

Do NOT open any Office application after setup finishes.

Run sysprep, with your custom sysprep.inf, and immediatly after it restarts,
use a GHOST floppy (with or without network) you created to take a GHOST of
the station.
I would recommend you use the Ghost enterprise product (7.5+) as it holds
much more then simple GHOST.

Print this (it is long...), read and then execute.

Safe deployment !

Arie H.

"Fletch" wrote:
 

reactivate office

Posted: 01 Dec 2004 12:13 PM PST

Fabri wrote: 


You could not find the work around...? So you couldn't see the "activate by
phone" option directly underneath the "activate by internet" then?! You must
be blind - or stupid.
--
Facon - the artificial bacon bits you get in Pizza Hut for sprinkling
on salads.