Error 1335

[Kemocer]

Hi everyone, i tried to install UT3 but during the installation Error 1335 was appearing, on forums people told me to install Microsoft Installer 3.5 Redistributable but during the installation storage error appears, I tried many solutions of those problems but none has worked.

 

[Zidane24]

Hi everyone, i tried to install UT3 but during the installation Error 1335 was appearing, on forums people told me to install Microsoft Installer 3.5 Redistributable but during the installation storage error appears, I tried many solutions of those problems but none has worked.

Are you sure you have enough Hard Disk space?

 

[H2SO4]

Task Manager, performance tab...

What do the "paged" and "nonpaged" kernel memory counters report just before/after you experience this error?

 

[Zidane24]

Task Manager, performance tab...

What do the "paged" and "nonpaged" kernel memory counters report just before/after you experience this error?

lmao...having reread their statement and yours...

I see/should have seen where this is going...

 

[Kemocer]

I have lots of Hard disk space. What about Error 1335?

 

[MacGyvr]

Information about this error as it pertains to installing Microsoft Office can be found here. The same informatin probably applies:

Smart Computing Article - Microsoft Office’s Error 1335

 

[H2SO4]

I have lots of Hard disk space. What about Error 1335?

The "storage" error you get during your attempt to update the installer is almost certainly completely unrelated to your disk. The actual error is Win32 status code 8:

Q:\>net helpmsg 8
Not enough storage is available to process this command.
​

The list of potential causes is many and varied, and running out of paged/non-paged pool is one of them. However with your numbers hovering around 100MB for paged pool and 32MB for NPP, that may not be the problem.

Try uninstalling your anti-virus first and then running the installer update. It's possible that the AV is interfering with memory allocation routines.

As far as the UT3 "1335" error is concerned, that's possibly going to be UT3-specific and not a Win32 status code. If you've been advised to update the installer, presumably there's an incompatibility between the older version and UT3. Hence, fixing the installer issue becomes the focal point.

 

[Flavius]

Which one Windows Installer did you try install?
This one CLICK or older this means 3.x.If you tried install any 3.x it's no strange it returned you "not enough storage" because this version is not for your system and it is normal - if any application is uncompatible with system during installation it can return error "not enough storage" as well

There never been Windows Installer 3.5

read there:
Released Versions of Windows Installer (Windows)

Besides in Windows 7 is buildin Windows Installer 5.0 (not even 4.5)What's New in Windows Installer 5.0 (Windows) and untill now if anybody have issue with this service can only fix it manually because there is no 5.0 to download...but I doubt is really issue with Windows Installer in this content

Relate to error 1335

Copy includes from DVD to hard disk to any location and from there try install

 

[MacGyvr]

Did anyone read the link I posted? It's not a hard drive space issue.

 

[H2SO4]

... if any application is uncompatible with system during installation it can return error "not enough storage" as well

It's a minor point, but no application should bail out of its setup routine with Win32 status 0x8 as a means of telling the user that "it's the wrong version".

You're the Update Master though, and the OP would do well to follow your advice

 

[H2SO4]

Did anyone read the link I posted? It's not a hard drive space issue.

I think everyone is aware of that, thanks.

0x80070008 = ERROR_NOT_ENOUGH_MEMORY = "Not enough storage is available to process this command."

I liked the way the guy (you linked to) starts off his troubleshooting by suggesting a good CD polishing though

 

[Flavius]

... if any application is uncompatible with system during installation it can return error "not enough storage" as well

It's a minor point, but no application should bail out of its setup routine with Win32 status 0x8 as a means of telling the user that "it's the wrong version".

I can sure you it is possible



Everybody get this message when try install Windows Installer 3.x on Vista or Windows 7 - If you don't believe me check yourself .When I tried install 4.5 on Windows 7 the message was different "The update is not applicable for your system" - I can instal 4.5 on Vista without any problem.

The same error you will get when you try install Windows Script on Vista (probably on Windows 7 as well I don't have time test all) - Windows Script installer is only for XP and older system.Probably the same error you get when try another things which are not applicable for your system.It's instalator of program issue not system issue.I'm not programmer to explain exacltly why it is. I only know from my experience.

So follow to your thoughts you can everybody prove to have "not enough storage issue" including yourself as well

 

[H2SO4]

... if any application is uncompatible with system during installation it can return error "not enough storage" as well

It's a minor point, but no application should bail out of its setup routine with Win32 status 0x8 as a means of telling the user that "it's the wrong version".

I can sure you it is possible

View attachment 33278

Everybody get this message when try install Windows Installer 3.x on Vista or Windows 7 - If you don't believe me check yourself .When I tried install 4.5 on Windows 7 the message was different "The update is not applicable for your system" - I can instal 4.5 on Vista without any problem.

Oh, don't get me wrong Flavius, I believe you entirely when you talk about the probable cause and the fact that it's "possible" to see this error message when attempting to install an inapplicable update.

My point is that it shouldn't happen, from a programming standpoint. The installer executable ought to be checking the target version and flagging any discrepancies with a meaningful bailout message ("Your OS doesn't need this particular update"), as opposed to dying in the a##e with a cryptic error status that nobody without a lot of experience and knowledge - such as yourself - would possibly associate with an incompatibility between the update and the OS in question