Not sure why you searched for Parser but try

If that's the case ...

What are the acccess rights of the directories and files in /home/phillip/perl5/lib/perl5 ?

IIRC files must be readable o+r , directories read and executable o+rx

See man chmod for details.

update

On another note: you should consider using a clean installation and not mixing system and private installations.

And please fix the missing code tag in your post

IIRC files must be readable o+r, directories read and executable o+rx

r is not strictly required for directories, missing read permissions on a directory only prevent you from listing the directory (ls and opendir will fail). To access items in a directory, you only need "cross" (executable) permissions on the directory, and sufficient permissions on the directory items.

For shared libraries (*.so), it actually depends on the OS implementation. Some Unix systems require them to be executable, for others, read permissions are sufficient. On Linux, you can have both variants, depending on the distribution.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

So is Perl accessing modules without checking the surrounding directory?

Probably...

At least in the case of perldoc - which is not relevant here - r would be needed on directories.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}

as the anonymous monk said, things need to be set up so that the cgi script can see your locally-installed libraries. I know that in my cPanel-based webhost-provider, I have to use cPanelUserConfig; or use a different shebang line, in order for it to know to look in the modules I've installed through cPanel. (see your own webhost-provider's documentation, because your version of cPanel may be different, or you may not be using a cPanel-based system)

Are you in fact using the same Perl executable for both command line and CGI? If not, that would explain your problems. The @INC looks like a system Perl, which would not normally look for modules in your personal directory.

If you are using the system Perl, you should use the system's package manager to install modules. Using the cpan client (or its variants) can cause considerable grief, as I have learned from sad experience, and as you may be learning now. If there is no package for this module, you should probably custom-build your own Perl, and that's not a bad idea anyway, as the previous responder pointed out.

If you are using a custom-built Perl, did you install it in a system-wide directory and then take the local::lib installer option when you initialized CPAN? You want the sudo option in this case.

Resolved: install the Spreadsheet::ParserExcel and Spreadsheet::WriterExcel manually.

"Using the cpan client (or its variants) can cause considerable grief, as I have learned from sad experience, and as you may be learning now. " I have learned just now, :-)

Thank for all your kindly help.