I ran across this error the other day while setting up a nested foreach loop. When looking at the error logs all I found was expecting T_PAAMAYIM_NEKUDOTAYIM. Which was not very helpful. If you find that you have this error, try looking for a missing dollar sign “$” on one of your variables.
Hope this helps, happy coding!
This post is a continuation of a previous post about the (8002AB0B) error that I received when trying to install almost any game downloaded over the PSN.
Last night I think I finnaly found the source of the error code that has plagued me the past few months. It came down to an Ethernet cable, once replaced everything worked great. The playstation website along with there customer service had never mentioned this as a possible issue, but if you are having this same error message I would suggest trying the following.
For me, I hooked up the ps3 directly into the cable modem first and used a different ethernet cable. I was able to download five games and install without issues. I noticed that the games that gave me the errors were the larger 1GB + games. Once I saw it worked hooked directly to the modem, I reconnected to through the router but with the new ethernet and downloaded a couple more games. So far all are working great now. The interesting thing is I could still connect and play online games fine with the bad cable, but it must have been corrupting the download data to cause the error.
Unfortunately the main reason to get this fixed was to play the new Uncharted 2 multiplayer beta which I had a key for. I got it installed only to see that the time period had expired.
Yet another error message today, this time when trying to send a message to a friend. I first received the message when I tried to reply to a message received. So I canceled out of the message, repeated the process and got the same error message, repeated and got it again for a third time. So I changed what I typed and it went through without a problem. So I tried one last time with the original message and the error came up once more. Maybe it was something I was writing? “what u doing ?” hardly seems like a message to cause problems. The message that did work: “hi”.
After a quick look online I found that some other people were having the same error. They recommended removing the punctuation from the end of the message, and sure enough it worked. To further test this I tried to send another message, “what u playing ?” and once again I got the error message.
To narrow the problem down this is what I think causes the issue. It is not the fact that there is a punctuation at the end of the message. But it is due to there being a space and then the punctuation by itself. “_?” When I remove the space the same message sends without a problem. So you might ask, why is there a space in the first place? When using the prediction that is to the right of the keyboard it will always put a space after the word to prepare for the next. So if your whole message is predicted… what u doing… then it will put a space after “doing”. If you don’t remove the space [square on the controller] before you put the punctuation then it will cause an error.
Update: So I have refined the problem a little further, it is not the fact that there is a space between the last word and a punctuation, but it is due to there being a space between the last work and a punctuation when the space was created due to the word predictor. If you put in a space your self, then it does not trigger the error. But if you use the word predictor and then a punctuation without removing the space, like clock work the error comes up.
Outlook could not connect to the server
Recently I encountered a problem with setting up emails at a large corporation with email hosted through mediatemple. The computers initially were able to connect, send and receive messages without a problem. But after a day or two we noticed some problems with the email. When the computers would try and connect, about 50% of the time they would error out with a message saying the server disconnected and you could not send or receive emails. This would last for about 5 minutes and then go away as if nothing happened.
There were a couple things I found out while troubleshooting this problem which helped to lead to the eventual solution.
Once I saw that all machines received the error at the same time I thought that their might be something limiting the amount of connections to the server. I called mediatemple to see if their was anything that might limit the connections to the email and sure enough there was. They gave me a link to a knowledge base article about how to increase the maxperip setting for the imap. The only problem is we werent using imap, it was pop3. They said that it didnt matter that it was for imap, it was used to control both… but it did matter and it did not fix the problem.
After some more searching around I found that there was a way to set the maximum connections per ip for pop3 email. The file was in the same folder and named pop3d. Essentially it was the same change mediatemple recommended but specific to pop3 email.
Once the change was made, and I restarted the mail services, the error went away and has only shown its head once in the last month and it immediately went away. If you are experiencing the same issue than the article in the knowledge base for resetting the imap courier connections is a great article and you can follow it almost word for word. All you need to do is make the same changes in the pop3d file instead of the imap file specified.
