Exchange Server 2003 freezes up

Hello,
Our Exchange server feezes up for the 4 consequtive weekends. We did a lot work in the last weekend to get our exchange to the better stage :  run all the firmware updates, bios.... However, the system failed to perform the defrag and generated the following error:defrag failed
      - Callback DLL not found: Unable to find the callback library jcb.dll (or one of its dependencies). Copy in the file and hit OK to retry
      - Operation terminated with error -2102 (JET_errCallbackNotResolved, A callback function could not be found) after 3353.16 seconds.
      - followed http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.admin/2007-10/msg00576.html

Any help in regards to narrowing down to the root cause would be respected.
Thank you,
Nikolina
nikolinaITAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
murgroupConnect With a Mentor Commented:
Also check the database size vs. database size limit in the registry.
http://www.petri.co.il/change_store_size_limits_ex2003_sp2.htm
 
0
 
Hypercat (Deb)Commented:
Did you register the new DLL file? See this post for reference:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21329635.html 
0
 
murgroupCommented:
I just had the same issue and same error with one of my customers. What I found was that the exchange databases were on different drives than the Exchange installation and bin folder. I moved the priv1.edb to the same drive as exchange install files ie. c\exchsrvr\mdbdata. The defrag worked fine.
Having said that I have many installations where the database is on dedicated disks and have never had a problem. Not sure why it was in this instance.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
nikolinaITAuthor Commented:
I need to talke a look at both answers, but will not be able to before tonight. Thank you for now.
0
 
nikolinaITAuthor Commented:
murgroup - it did not work
0
 
murli30Commented:

Copy the jcb.dll files form Exchange 2003 sp2 setup files to bin folder

+ Also if you have more than 4 GB of memory on your Exchange server then add /3gb switch in boot.ini file

 /3GB /USERVA=3030 in boot.ini file
0
 
nikolinaITAuthor Commented:
We will try this murli30. Thank you, NI
0
 
murgroupCommented:
I forgot to tell you I also added the 3G switch to boot.ini file. One of murli30 suggestions should work.
0
 
nikolinaITAuthor Commented:
thank you murgroup, we will do the work tonight including murli30's suggestions. I will let you know the results.
0
 
nikolinaITAuthor Commented:
Hi, below is the recomendation I got .......

The /3GB switch is not recommended on an SBS server.  This is an option for an Exchange Server (a stand-alone dedicated one), or if there are very specific memory and database issues.  Here is a link for your review - http://blogs.technet.com/sbs/archive/2006/06/30/439628.aspx.  Also, the /3GB switch will not work until the server is rebooted.

As your Exchange database is not corrupted (if it was, you wouldn't be able to do much and there would be various error messages generated), then the /3GB switch is not a modification we recommend.  You are also not running out of virtual memory or paging space either.

Although Windows Small Business Server is the cumulation of a Windows Domain Controller, File Server, SQL Server, Sharepoint 2.0 & Exchange, not all articles for each individual component can be or are recommended for an SBS server.  The site - http://blogs.technet.com/sbs/default.aspx - is one site that is a very good resource for SBS versions.

Microsoft TechNet and other resources usually specify if it is for Exchange and/or SBS.  If it doesn't say SBS, then it needs to be researched to see if there is a possible conflict one one of the other components.

With regards to copying a new copy of the JCB.DLL over, we can certainly do that but Exchange SP2 was reapplied (which would have updated it) as well as we transfered the JCB.DLL for our SBS server as well to elminate the chances your original one was corrupted.

Microsoft deals with per incident issues.  Meaning we can open a ticket with them (the last time I checked it was about $300 per incident) and they will stick with it until there is a resolution or if it can't be fixed, they do not charge (at lease that was the policy).  As we have received the USB drive from you with the DB copies, I would prefer to perform some more invasive tests to see if we can defrag your PRIV1.EDB database first.

Please advice,
Nikolina
0
 
murgroupCommented:
Since you don't mention who sent you this I will assume it was Microsoft. Of coarse it sounds like great advice and you should persue a resolution with them.
I won't take issue with anything they said but will say that I and many other experts use the 3GB switch on SBS and it works fine. Yes, when applying fixes you should always make sure that it is approved for your product. Over the years I have found SBS to be very friendly to updates and fixes. Nothing I have tried has ever crashed an SBS server. Now that's not to say I don't do very extensive research before applying a fix.
Also as stated above I encountered this same issue two days ago with a customer SBS 2003 server and was able to fix it as described. I was able to run an integrity check and the database was ok. I just could not defrag it.
When I give advice it's not just to get points. Most experts here genuinely want to help you resolve your issue. If I thought it would harm your system not only would I not comment, the forum admin's would jump in and tell me I am wrong.
Good luck,
 
0
 
murli30Commented:

Yes i completly agree with what Master has said

It's not that we contibute for points

The solution provided are given after the experts have worked on real life scenario...)
No Hard feelings,

Exchange Rocks
0
 
nikolinaITAuthor Commented:
This totaly needs clarification from my side.
We had an issue with our Exchange server freezing up sitting on the same box with SBS. There is a consulting company that is supposed to take care of this issue and I do not see as much commitment as I would like and feel comfortable that an issue will be resolved. That is why I opened up the question here to here from the Experts what they think. Response I posted ( the long Email ) was sent to me from the comsultant after I sent them murgroup's suggestion. So it is not that I do not trust your solutions, I just thought you would be open to comment on my post from the technical perspective.
Thank you on your support.
0
 
murgroupCommented:
NikolinaIT,
Thanks for the clarification. My wife told me I was cranky/moody yesterday so that is probably what caused the strong response.
Hopefully your consultant will step-up and fix the issue. I'm sure they are good at what they do but it's always good to keep tabs on them and question what they are doing. You should also let them know your not pleased with the level of support your getting and if they want to keep you they need to show their commitment.
Best regards,
Murgroup
0
 
nikolinaITAuthor Commented:
Ha, ha.... o.k. we are good now!
I hope my consultants will push more toward solutions rather than keeping the problems under the surface, and I have no idea when again this will come up.
I have one more doubt about the solution here, Exchange did not freezed up since last week, which looks like a good sign, but they(consultants) couldn't defrag it. How unstable DB is if it can not defrag and should I push till they defragment it?
Thank you,
Nikolina
0
 
nikolinaITAuthor Commented:
exchange server was frozen this morning, started around 4:00 a.m. i had to physicaly reboot it.
0
 
nikolinaITAuthor Commented:
We have AVG 9.0 installed on our Exchange. Our next step is to remove the anti virus - I was convinced that it is o.k. and that our network is safe without it. Also CDP is doing backup, so we will temporarly disable backup this week and see if the freezing stops.
0
 
nikolinaITAuthor Commented:
Thank you murgroup. Currently we are at the 38% out of the maximum size.
Also, AVG has been removed as well as CDP backup. Now we are going to wait.
0
 
nikolinaITAuthor Commented:
This weekend no problems, but waiting till Wednesday since it will be full 7 days since the last reboot.(normaly problems occured in 7 days cycles)
0
 
nikolinaITAuthor Commented:
Again the same issue. However, this time we capture more in our log file. It is pointing to the Sync and CDP. I was mistaken when I said that we removed(disabled) CDP last time. We did not do it, and we are doing it now.
0
 
murgroupCommented:
Interested to see if this fixes it. Keep us posted.
0
 
nikolinaITAuthor Commented:
Sure, we are going to give it another 7 day cycle try. Normally it happens every 7 days ( i will start hating the number seven !) I will keep you posted. If the problem reoccures we will open up a ticket with Microsoft.
0
 
nikolinaITAuthor Commented:
In the last 7 days we did not have any issue, and tonight we are going to try live defrag of the db
0
 
murgroupCommented:
Sounds like your getting close to a solution. Let us know how the defrag goes.
0
 
nikolinaITAuthor Commented:
We were able to defrag. This problem has been narrowed down to ActiveSync and CDP backup issue.
Thank you on your support
0
 
nikolinaITAuthor Commented:
A big part of this solution came as a result of me and internal consultant guessing. For this reason I think it is fair to give a grade B solution.
0
All Courses

From novice to tech pro — start learning today.