in reply to "MSVCR90.dll not found" Error Message

The first error message arises because you've compiled DateTime using VC9 and one the resulting DLLs requires the VC9 CRT, but that it cannot be found.

The second error message means either:

Copying DLLs around is not the right way to fix this. Indeed, preventing people from doing that is the primary reason for the whole manifest process to exist.

The first thing you should try is re-building, testing and installing the DateTime module(s).

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"I'd rather go naked than blow up my ass"
  • Comment on Re: "MSVCR90.dll not found" Error Message

Replies are listed 'Best First'.
Re^2: "MSVCR90.dll not found" Error Message
by roho (Bishop) on Mar 28, 2010 at 22:33 UTC
    Thanks for the explanation and suggestion. I re-installed DateTime from the ActiveState repository using ppm install DateTime --force but unfortunately I still get the error message. I also tried re-installing VC9 in hopes that its installation process would re-install MSVCR90.dll, but it did no good. This is a tough one.

    "Its not how hard you work, its how much you get done."

[reply]

      FWIW: I think the problem lies squarely with the build process for the DateTime module. I just tried to install the module here, and it failed miserably. It use Build.pl instead of the usual makefile.pl, and that seems to be completely broken for Windows. 

      C:\Perl32\packages\DateTime-0.55>build
cl : Command line warning D9035 : option 'Wp64' has been deprecated an
+d will be removed in a future release
cl : Command line warning D9035 : option 'Wp64' has been deprecated an
+d will be removed in a future release
compilet-1271857152.c
C:\Users\Nigel\AppData\Local\Temp\compilet-1271857152.obj : fatal erro
+r LNK1112: module machine type 'X86' c
Checking prerequisites...
  build_requires:
    !  Test::More (0.86) is installed, but we need version >= 0.88

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the v
+ersions
of the modules indicated above before proceeding with this installatio
+n

Run 'Build installdeps' to install missing prerequisites.

Creating new 'MYMETA.yml' with configuration results
Creating new 'Build' script for 'DateTime' version '0.55'

C:\Perl32\packages\DateTime-0.55>build installdeps
Too early to specify a build action 'installdeps'.  Do 'Build installd
+eps' instead.

      [download]

      Don'tcha just love that last error :)

      So then I installed the latest version of Test::Simple, which went successfully and then re-tried Build.pl for DateTime and it reports the same dependancy:

      <Reveal this spoiler or all in this thread>

      Module::Build is just broken and should be consigned to the scrap heap.

      Personally, I could never recommend any module (DateTime) that requires 1390 files to be installed (as a binary distribution), just to manipulate a few dates. A typical example of O'Woe.

      Use Date::Manip instead. It's old and crusty, but it works.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]
        I would love to set it aside, but 5 other modules require it, one of which (HTML::FormFu) I'm using as I'm learning Catalyst. The upside is that (so far) this error doesn't seem to affect the execution of the module. The correct date and time are rendered from it, but there is obviously no way this constant error messsage display will be acceptable in a production environment. I'm going to look on the MS web site for the proper way to get this dll from the "\windows\winsxs" directory to where it should be.

        "Its not how hard you work, its how much you get done."

[reply]
      I re-installed DateTime from the ActiveState repository using ppm install DateTime --force but unfortunately I still get the error message

      So ... you probably have now installed a version of DateTime that has no dependency on MSVCR90.dll - from which we deduce that the error message is coming from some *other* module that DateTime loads (and which was, presumably, built using VC9). Are there no other error messages (in the cmd console, for instance) that provide additional information ?

      If you want to continue going down the 'ppm install' path, I think you need to identify the module(s) that's causing the problem, and then 'ppm install' it with '--force'.

      You can test various modules by running (eg) perl -MList::MoreUtils -e 1
      If List::MoreUtils were the culprit, that would be enough to generate the error. Or, in a script, simply use List::MoreUtils; would be sufficient (iff List::MoreUtils were the culprit).

      Cheers,
      Rob
[reply]
[d/l]
[select]
        Thanks for your suggestion, Rob. The Params::Validate module was the one causing the MSVCR90.dll error messages. I re-installed it from AS repository using ppm and the error message is no longer displayed. What was a bit odd was that Params::Validate 0.95 was already installed on my machine, but running the command 'ppm install Params-Validate' (re-)installed the module without requiring --force and without issuing any warnings about the module already existing. Thanks again for your help. Roy.

        "Its not how hard you work, its how much you get done."

[reply]

In Section Seekers of Perl Wisdom