Just how much does a premier contract cost? When you are a manufacturing company of less than 300 people, I doubt you can afford it.
So far all this discussion does is warn me to stay away from SharePoint. Kurt On Fri, Jul 31, 2009 at 07:24, Brian Desmond<[email protected]> wrote: > A lot of this is also a function of the fact that you get totally different > support if you’re calling on a pro case (when you call and put it on a > credit card) versus a premier contract. Premiere support comes with SLAs, a > TAM to complain to, etc. The pro cases folks are outsourced and come with > none of that. You get what you pay for essentially… > > > > Thanks, > > Brian Desmond > > [email protected] > > > > c - 312.731.3132 > > > > From: Rob Bonfiglio [mailto:[email protected]] > Sent: Friday, July 31, 2009 9:03 AM > To: NT System Admin Issues > Subject: Re: Is there a SharePoint Expert that can help me out? 2.0 - 3.0 > PROBLEMS > > > > I had a call once that last for about 12 hours...but that was mostly b/c the > SharePoint engineer didn't seem to know much about SQL...after about 10-11 > hours of working he got a SQL engineer on the phone and it was fixed pretty > quickly. > > On Fri, Jul 31, 2009 at 9:42 AM, Carol Fee <[email protected]> wrote: > > +1 on that. You really did get lucky. PSS for SharePoint and MOSS is not > spiffy. > > > > CFee > > > > > > ________________________________ > > From: Ken Schaefer [mailto:[email protected]] > > Sent: Thursday, July 30, 2009 8:05 PM > > To: NT System Admin Issues > Subject: RE: Is there a SharePoint Expert that can help me out? 2.0 - 3.0 > PROBLEMS > > > > Four hours is nothing ;-) > > > > We’ve had PSS calls open for weeks with SharePoint. Had another SharePoint + > DPM issue that went all the way back to the PGs to have them figure out > which of the two products (or how they were interacting) was breaking DPM. I > think that was 6 weeks all up. > > > > Cheers > > Ken > > > > From: Marty Nelson [mailto:[email protected]] > Sent: Friday, 31 July 2009 1:03 AM > To: NT System Admin Issues > Subject: RE: Is there a SharePoint Expert that can help me out? 2.0 - 3.0 > PROBLEMS > > > > I ended up on the phone with MS for four hours so something went really > wrong and thank god they knew where to fix it! > > > > Thanks again for the suggestions. > > > > -Marty > > > > From: Ken Schaefer [mailto:[email protected]] > Sent: Wednesday, July 29, 2009 6:20 PM > To: NT System Admin Issues > Subject: RE: Is there a SharePoint Expert that can help me out? 2.0 - 3.0 > PROBLEMS > > > > The Configuration Database is an SQL Server (or MSDE) database somewhere. > It’s usually called SharePoint_Config (for MOSS at least). So, you have to > have SQL Server or MSDE somewhere, and it needs to be hosting this database. > > > > You can run the SharePoint Technologies Configuration Wizard to reconnect to > the database, but you obviously need to know what your SQL Server > name/instance is... > > > > Cheers > Ken > > > > From: Marty Nelson [mailto:[email protected]] > Sent: Thursday, 30 July 2009 3:49 AM > To: NT System Admin Issues > Subject: RE: Is there a SharePoint Expert that can help me out? 2.0 - 3.0 > PROBLEMS > > > > Sorry, a little more info. This is running on a W2K3 SP@ machine with IE7. > Now it’s degraded to the point to where I cannot even connect to the central > management page. Says “Cannot connect to the configuration database.” > > > > Now when I set this up originally YEARS ago, I accepted all of the defaults > and now have no idea where the data resides. I have ~* very lightly used > SharePoint sites, none of which are available at the moment. > > > > This database error is a new phenomenon since I last posted > > > > Thanks, > > > > -Marty > > > > From: Marty Nelson [mailto:[email protected]] > Sent: Wednesday, July 29, 2009 10:20 AM > To: NT System Admin Issues > Subject: Is there a SharePoint Expert that can help me out? 2.0 - 3.0 > PROBLEMS > > > > So I started the workup to this upgrade yesterday. Got all of the prereq > stuff loaded, ran a prescan everything came back dandy. Ran the upgrade, > looked like it finished with no problems. And that’s where it fell off of > a cliff. Looking at the upgrade.log file there are some errors and > failures, but I have no idea what it means, much less how to fix them. If > there’s anyone out there that can help me out I would greatly appreciate it! > > > > FWIW, these are the instructions I’ve been following: > > > > http://technet.microsoft.com/en-us/library/cc424954.aspx > > > > PLEASE HELP! > > > > -Marty > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
