SysConfig won't save settings

[knischan]

Hi. I know I must be making some boneheaded mistake, but it's rather frustrating. I went to sysconfig, searched for logo. Went to Frontend::Agent. I made sure AgentLogo is checked then updated the data to reflect my custom logo. Went down and hit update. It thought about it for a few seconds, then refreshed the page with the original settings back again. What am I doing wrong?? Thanks

[crythias]

Make sure the entry isn't hard defined in Config.pm

[knischan]

Hmm. Did a search for "logo" and "url" in Config.pm, no results. Frustrating, because I can customize my OTRS OnDemand no problem, but when I do the exact same steps to customize my local hosted one I get this problem where it reverts the settings. *sigh*

Auugh, I just found that it applies to any configuration setting. I went to Core and it had FQDN for the system as yourhost.example.com so I changed that, hit update and it reverted too. *sob* I thought mayhap it saves settings in the database, and since I changed to MSSQL I thought perhaps it's not accessing the DB right. However, I created an agent and it worked fine so I assume it's not that.

PS, also confused as to why the FQDN was example. When I ran the web setup, I did specify the proper FQDN. Something must be rather awry somewhere.

[crythias]

Then it could be permissions on Config.pm Make sure otrs can write to it (check System Log as well)

[knischan]

OK, found out something. If I go into SysConfig and make a change, I then hit apply and when the screen refreshes the data are still reverted. At that point, I switch to my RDP window to the server and do a net stop w3svc to stop IIS, then whence stopped I restart it. Going back to my browser, I hit overview. Click Frontend::Agent to go back, and voila... the data I entered, which it rejected and had reverted to defaults, is now set.

Sooo, it apparently is saving my requested changes somewhere but it takes cycling IIS for the system to show the change. What the world would cause that?

[knischan]

Any ideas? Maybe the application pool worker is locking the file somehow? (Really stretching now). I found that rather than restarting all of IIS I can just go into the app pools and restart the OTRS application then the changes are visible on the site. I pulled up Process Monitor and watched whilst I made a change to Core in SysConfig, everything looked like it saved fine. I can open zzzauto.pm and see my desired change has been saved. I can rename the file to something else though, so I guess a file lock isn't the issue. It isn't cache related either, as I can fire up IE after making the change in Firefox and still see the original data.

[r00ki3]

I have exactly the same problem, sysconfig won't update without a IIS 7.5 Restart, any ideas how to solve this problem?

Best Regards Mike

Update:

I found out that c:\Perl\bin\PerlEx30.dll will cause this problem, when u change to c:\Perl\bin\perl.exe "%s" %s, sysconfig will update great! maybe this is a bug?

[friendlypenguin]

I had exactly the same behavior when I used OTRS 3.0.9(later 3.1.6) together with httpd 2.2.3 on Centos 5.8 and SPEEDYCGI. When I switched to mod_perl2 everything worked fine...

[richardn]

I dont know if im in the right Thread, but im facing a similar problem:

I want to make changes in the ZZZAAuto.pm (Change the Order of the TicketMenuLinks), when I overwrite the files everything works as expected, but when I enter the config in Ticket::Frontend::MenuModule everything gets back to where it was :/

I also tried to stop/restart Apache and otrs service (CentOS) but that didnt change anything....

any suggestions?

[jojo]

the ZZZAAuto.pm is autogenerated, you can not change it manually.

Put your changes in Config.pm