Help Please...Can not access Admin Pannel

kawsakimx6

I tried searching, but did not find my exact problem. I have found ones that were close, but nothing that i could figure out.

All that being said, like the title says, i can not access my admin panel. it was sending me to a blank screen so i turned warnings on and received this.

Warning: require_once(Mail/mimeDecode.php) : failed to open stream: No such file or directory in /home/www/web230/html/swissgourmetclub/osTicket/include/class.mailparse.php on line 19

Fatal error: require_once() : Failed opening required 'Mail/mimeDecode.php' (include_path='.') in /home/www/web230/html/swissgourmetclub/osTicket/include/class.mailparse.php on line 19

I fdo have the file class.mailparse.php in the directory where it needs it so i am a bit confused.

I am not a php wiz, and not not claim to be. I am more on the marketing side of the business with knowledge in HTML and Java. I am however tasked with getting osTicket up and running, so any help would be awesome!

Thanks

ntozier

You appear to be getting to the login prompt (or at least I am). I don't have a username and password to try to get farther than that. :)

Have you checked the existence and permissions on

include\pear\Mail\mimeDecode.php

kawsakimx6

I can get to the login screen, and can even get /osTicket/scp/index.php to come up but when i try to go to the Admin Panel it tosses that code.

I have also checked the include\pear\Mail\mimeDecode.php and it is there, and set to (Owner - Read, Write) (Group - Read) (Public - Read) I have also changed the public to write, but seems that it is not the case with the same warnings getting tossed.

I can get you Username access and just change it later if you think that looking at it, you could help me.

kawsakimx6

with a bit more searching. i have found the answer. I hope this helps others out there..

http://osticket.com/forums/archive/index.php/t-6532.html(http://osticket.com/forums/archive/index.php/t-6532.html)

Grizly

That was a 1.6 solution.

kawsakimx6

That was a 1.6 solution.

yes it was, which is why i did not think it was going to work. However it is what got me going.....So, I'll take it!

ntozier

Huh. I think that maybe it is a PHP configuration issue, which would explain why its not reported very often.

Do you have access to your php.ini?