OFFXPDEV Packaging Wizard Error 5

[Martin Schell]

Hallo,

for about one year I have this problem and I'm not be able to solve it:

Situation:

clean 333-Celeron-PC with
- Windows XP Pro SP 1
- Office XP Pro SP2
- Office XP Developer SP1
- all Windows and Office patches are installed

Problem:

When the packaging wizard starts to copy the files, it allways shows that
message:
'Error 5: Invalid Procedure Call or Argument.'
- no matter whether started from start menu or from an office application,
- no matter whether it concerns a Word, Excel or Access project.

In addition:

I know KB article 326127. None of the conditions noted there for this error
is given:
- target folder is not compressed
- Office as well as Office Dev. are from my MSDN-Abo of 2002
- the test projects are empty
- there is enough disk space

The message appears after coping setup1.exe to folder ...\Package\Support.

Now I urgently need a running installation for an actual access project.

Thanks and greetings
Martin

 

[Tony Toews]

When the packaging wizard starts to copy the files, it allways shows that
message:
'Error 5: Invalid Procedure Call or Argument.'

Do you have two files with the same name in two different directories
when you built the image? Such as readme.doc in the main folder and
readme.doc in a subfolder? Just a guess.

Ah, someone else had the problem and posted the following.

"Invalid Procedure Call or Argument" during setup created by MOD XP

Problem Solved, hope this solution might help someone else...

Error was caused by adding quote marks around the path to the mdb in
the command line of the icon configuration in the PDW. i.e.

This causes the setup error: "$(ARTFolder)\MSAccess.exe"
"$(AppPath)\MyDb.mde"

This is OK: "$(ARTFolder)\MSAccess.exe" $(AppPath)\MyDb.mde

Quote marks around the path to the Access.exe appear to be acceptable
but not around the mdb path..!!

Cost me a whole day :-[

MP

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Martin Schell]

Hi Tony,

Of course, for testing purposes, I used only one single project file, and I
left untouched the PW defaults.

Thanks for effort
Martin

When the packaging wizard starts to copy the files, it allways shows that
message:
'Error 5: Invalid Procedure Call or Argument.'

Do you have two files with the same name in two different directories
when you built the image? Such as readme.doc in the main folder and
readme.doc in a subfolder? Just a guess.

Ah, someone else had the problem and posted the following.

"Invalid Procedure Call or Argument" during setup created by MOD XP

Problem Solved, hope this solution might help someone else...

Error was caused by adding quote marks around the path to the mdb in
the command line of the icon configuration in the PDW. i.e.

This causes the setup error: "$(ARTFolder)\MSAccess.exe"
"$(AppPath)\MyDb.mde"

This is OK: "$(ARTFolder)\MSAccess.exe" $(AppPath)\MyDb.mde

Quote marks around the path to the Access.exe appear to be acceptable
but not around the mdb path..!!

Cost me a whole day :-[

MP

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews]

Of course, for testing purposes, I used only one single project file, and I
left untouched the PW defaults.

Do you have the MOD SP1 installed?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Martin Schell]

Hi Tony,

[...]

Do you have the MOD SP1 installed?

see my posting

Martin

 

[Chris Mills]

I have seen postings about "Error 5" occasionally through the years. And just
to make myself *really* usefull I can't remember whether there was just one
resolution :-( I seem to think it was more to do with language mis-matches.

Try a search on
http://groups.google.com/groups?oi=djq&as_ugroup=comp.databases.ms-access (for
instance) which has a better history. One thing I immediately found was:
"
Try "MOD2000: "Invalid Procedure..." Packaging DB w/ Linked Tables [Q304652]"
at the
Knowledge Base at support.microsoft.com.

This can also be caused by having ODE 97 installed on your system concurrently
with
MOD XP.

Make sure you DO NOT have compression on your package directory, or on
the language component directory which you specify.
"
(oh, that was posted by Tony!!!)(he DOES get around!!!<chuckle>)

If the history of this known error can't help, then nothing can (it's my
thought for the day)

Hi Tony,

[...]

Do you have the MOD SP1 installed?

see my posting

Martin