[solved] Upgraded from 1.3.2 to 1.4: now pictures don't always show

[Klassiekerrally]

As said in the subject: after upgrading to the newest version, most of the time the pictures on my website (www.klassiekerrally.nl) don't show.
This affects the complete look of my site (ofcourse), so is there a quick way to solve this, or am I the only one that can't see the pics?

[Signex]

did you accidently delete the uploads/images folder when you updated?

[alby]

As said in the subject: after upgrading to the newest version, most of the time the pictures on my website (www.klassiekerrally.nl) don't show.
This affects the complete look of my site (ofcourse), so is there a quick way to solve this, or am I the only one that can't see the pics?

I see (for example): http://www.klassiekerrally.nl/uploads/i ... erding.jpg
an:
HTTP Error 500
IISPassword for Internet Information Services

Alby

[Klassiekerrally]

How can an upgrade cause that, and what can I do to fix it? (I'm not that technical, I might have to ask the right questions to my webhosting company)

[alby]

How can an upgrade cause that, and what can I do to fix it? (I'm not that technical, I might have to ask the right questions to my webhosting company)

Depend to your operations.
Check in Admin for System Information for other infos

Alby

[Klassiekerrally]

A lot of info!
CMS Install Information:
CMS Version 1.4

Config Information
php_memory_limit:
process_whole_template: true
max_upload_size: 12000000
default_upload_permission: 664
assume_mod_rewrite: false
page_extension:
internal_pretty_urls: false
use_hierarchy: false
root_url: http://www.klassiekerrally.nl
root_path: c:\inetpub\wwwroot\Klassiekerrally
previews_path: c:\inetpub\wwwroot\Klassiekerrally\tmp\cache (0777) Succes
uploads_path: c:\inetpub\wwwroot\Klassiekerrally\uploads (0777) Succes
uploads_url: http://www.klassiekerrally.nl/uploads
image_uploads_path: c:\inetpub\wwwroot\Klassiekerrally\uploads\images (0777) Succes
image_uploads_url: http://www.klassiekerrally.nl/uploads/images
use_smarty_php_tags: false
debug: false
locale:
default_encoding:
admin_encoding: utf-8

PHP Information:
PHP Safe Mode (safe_mode): Off (Nee) Succes
Current PHP Version (phpversion): 5.1.2 Succes
PHP Effective Memory Limit (memory_limit): 16M --Add Me - caution --
Maximum Execution Time (max_execution_time): 300 Succes
GD version (gd_version): 2 Succes
Session Save Path (session_save_path): c:\inetpub\wwwroot\Klassiekerrally\admin/lang (0777) Succes
Checking if the httpd process can create a file inside of a directory it created (create_dir_and_file): Succes
PHP Open Basedir (open_basedir): Succes
Maximum Post Size (post_max_size): 8M --Add Me - caution --
Maximum Upload Size (upload_max_filesize): 12M Succes

Server Information:
Server API (server_api): cgi-fcgi
Server Database (server_db_type): MySQL (mysql)
Server Database Version (server_db_version): 5.0.22 Succes
Server Software (server_software): Microsoft-IIS/6.0
Server Operating System (server_os): WINNT 5.2 On i586

Permission Information
tmp: c:\inetpub\wwwroot\Klassiekerrally\tmp (0777) Succes
templates_c: c:\inetpub\wwwroot\Klassiekerrally\tmp\templates_c (0777) Succes
modules: c:\inetpub\wwwroot\Klassiekerrally\modules (0777) Succes
Bestandscreatiemasker (umask): c:\inetpub\wwwroot\Klassiekerrally\tmp\cache (0777) Succes
config_file: 0444 Succes

[alby]

image_uploads_path: c:\inetpub\wwwroot\Klassiekerrally\uploads\images (0777) Succes

Here report all ok (with permission of write file)

Server API (server_api): cgi-fcgi

Here con FastCGI many have problems but not in install DB

Alby

[Klassiekerrally]

Server API (server_api): cgi-fcgi

Here con FastCGI many have problems but not in install DB

But I didn't have problems before updating to 1.4. Is it a 1.4 specific problem?
In that case: Can I go back to 1.3.1 again?

[alby]

Server API (server_api): cgi-fcgi

Here con FastCGI many have problems but not in install DB

But I didn't have problems before updating to 1.4. Is it a 1.4 specific problem?

Nope, many users report, with old versions, for memory problems

In that case: Can I go back to 1.3.1 again?

Yes, restore DB and replace all files

Alby

[Klassiekerrally]

Solved. My webhoster reset all IIS values. Somehow I managed to change them while upgrading to 1.4!

How can I prevent that next time?

[alby]

Solved. My webhoster reset all IIS values. Somehow I managed to change them while upgrading to 1.4!

How can I prevent that next time?

It's webhoster problem.
CMSMS cannot change IIS settings 

Alby