hi there
I faced the problem - instalaton was incorrectly executed.
After writing log-file I found messages similar with "Error 1720. Microsoft VBScript runtime error. Access disabled: 'Session.Property'" or something like that (installation was executed in Russian language - messages in russian).
All my CustomActions containing Session.Property-string are fails with that error.
What it could be? Any ideas?
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Error "Access disabled: 'Session.Property'"
Started by
nesesser
, Nov 27 2006 12:26
6 replies to this topic
Glytzhkof
-
- Moderators
- 1,447 posts
Posted 27 November 2006 - 14:23
Are you using deferred mode custom actions?
Regards
-Stein Åsmul
-Stein Åsmul
nesesser
-
- Full Members
- 62 posts
Posted 27 November 2006 - 14:51
| QUOTE (Glytzhkof @ 2006-11-27 14:23) |
| Are you using deferred mode custom actions? |
Either deferred or non-deferred mode custom actions returned similar messages.
The only similar point in this CA's is working with Session.Property method.
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 27 November 2006 - 21:00
Can you post the relevant line of your VBScript code?
And your custom action is actually Immediate, not Deferred, Rollback or Commit?
And your custom action is actually Immediate, not Deferred, Rollback or Commit?
Stefan Krüger
InstallSite.org twitter facebook
nesesser
-
- Full Members
- 62 posts
Posted 28 November 2006 - 07:07
| QUOTE (Stefan Krueger @ 2006-11-27 21:00) |
| Can you post the relevant line of your VBScript code? |
Here is a full text of one of my CA's, that was performed unsuccesfully:
| CODE |
| '===================================================================== ' Initialization CR-character '===================================================================== Session.Property("CR") = Chr(13) + Chr(10) |
| QUOTE (Stefan Krueger @ 2006-11-27 21:00) |
| And your custom action is actually Immediate, not Deferred, Rollback or Commit? |
According to Custom Action In-Script Execution Options all my CA's are Immediate.
And I actually forgot to mention that this installation worked sucessfully on other machines. This accident occured only once. But is very significantly to find out what the point is.
Glytzhkof
-
- Moderators
- 1,447 posts
Posted 28 November 2006 - 10:27
I have seen blocking of VBScript code on machines with particularly aggressive anti virus scanners. MSI is its own VB scripting host, so it should not depend on the system's installation of VBScript, but I suppose there could be some group policy setting that disables also MSI's scripting engine. I would try to disable anti virus and then test again.
Regards
-Stein Åsmul
-Stein Åsmul
nesesser
-
- Full Members
- 62 posts
Posted 29 November 2006 - 12:53
Thks on reply.
Then the question is what kind of group policy could influence on this situation?
And I'm not sure that AV-scanner was the reason of this occasion - it was disabled during installation.
Then the question is what kind of group policy could influence on this situation?
And I'm not sure that AV-scanner was the reason of this occasion - it was disabled during installation.
Edited by nesesser, 29 November 2006 - 12:57.