Jump to content


Photo

Internal error 2235


  • Please log in to reply
6 replies to this topic

#1 Jann

Jann
  • Members
  • 35 posts

Posted 05 October 2001 - 10:52

I have an install which creates a virtual directory.  I know that the scripts work because I have used them in previous installs and I have checked them externally as well.

When I run the install I get the error message:
Internal Error 2235, RuntimeFlags, SELECT 'Component', 'RuntimeFlags', 'KeyPath' FROM 'Component' WHERE 'Component' = ?

When looking up the error it seems to imply it is something to do with SQL which this script has nothing to do with.

Thanks

Juliet


#2 Jann

Jann
  • Members
  • 35 posts

Posted 05 October 2001 - 16:58

I have another error on another install now.  It is:
Error 1406.  Could not write value VersionMajor to key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\currentVersion\Uninstall\{number}

Verify that you have sufficient access to that key or contact support.

It isn't that I don't have access to the key as I have admin access on my PC.

Installshield had problems when I installed W2000 SP2 and IE6.  It seemed to work when I reverted back to IE5.5 but now I keep getting errors on installs that used to work.

Please help, thanks.


#3 Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,259 posts

Posted 05 October 2001 - 17:00

Are you sure there is a column RuntimeFlags in table Component? Is it added at runtime?

#4 Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,259 posts

Posted 05 October 2001 - 17:02

What ProductVersion did you enter?

#5 Jann

Jann
  • Members
  • 35 posts

Posted 08 October 2001 - 09:20

I'm not actually doing anything with a database and so I don't even have a table called component.

All it is is a vb script which creates a virtual directory.

I put VersionNT as a condition.

I had a whole load of problems with Installshield not being compatible with IE6.  I'm wondering if these problems are anything to do with that or W2000 SP2 which I also installed.

I m now back to using IE5.5 which is better.

The installs used to work before I installed SP's etc.


#6 Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,259 posts

Posted 09 October 2001 - 15:07

The error message is about a SQL query used in a custom action. The MSI file is a database. If you didn't create the custom action, then there might be a problem with a merge module.

#7 Jann

Jann
  • Members
  • 35 posts

Posted 10 October 2001 - 09:57

There are no merge modules in my project, I have double checked this.

This is the script from the custom action which I have used:

dim oIIS,oVirtualDir,WebVirtualDirectoryName,WebPath
' Create a new IIS Virtual Directory called clickstreamnt
WebVirtualDirectoryName="clickstreamnt"
' change c:\ to you choice of physical directory path here....
WebPath="c:\program files\clickstream technologies\clickstream"
'
Set oIIS = GetObject("IIS://LocalHost/W3SVC/1/root")  '  
Set oVirtualDir = oIIS.Create("IIsWebVirtualDir", WebVirtualDirectoryName)
oVirtualDir.Path = WebPath
oVirtualDir.KeyType="IIsWebVirtualDir"
oVirtualDir.AccessRead = True
oVirtualDir.AccessWrite = False
oVirtualDir.AccessExecute = False
oVirtualDir.AuthAnonymous = False
oVirtualDir.AuthBasic = True
oVirtualDir.AuthNTLM = True
oVirtualDir.ContentIndexed = False
oVirtualDir.EnableDirBrowsing = False
oVirtualDir.AppIsolated = False
If InStr(1, oVirtualDir.DefaultDoc, "Default.asp") = 0 Then
oVirtualDir.DefaultDoc = "Default.asp, " & oVirtualDir.DefaultDoc
End If
Call oVirtualDir.AppCreate(True)
oVirtualDir.AppFriendlyName = WebVirtualDirectoryName
Call oVirtualDir.SetInfo()
Set oVirtualDir = Nothing
Set oIIS = Nothing