adamf

We are currently experencing a problem with the spooler service using anywhere between 30-50% CPU which in turn is causing documents not to be printed, error messages relating to the printer having not yet responded or it ends up crashing the application you are trying to print from. There has been no new printers or drivers added and this problem seems to have just occured. Any ideas?

Ok..... That worked in fashion.... I'm getting this now: PXE-T04: Access Violation PXE-E36: Error recieved from TFTP server Any ideas?

I've started to play around with SCCM 2007, i've got it setup and am able to distribute software to clients without a problem. I'm now trying OSD and running into problems booting from PXE/getting a response from the SCCM. This is what I have done so far, hopefully someone can point me in the right direction.... SCCM is setup, installed on our servers VLAN, the client I am testing it with is on another VLAN and has the client installed. WDS has been installed and not configured on the SCCM server I've created PXE service point and add the 2 images that come with SCCM to the DP (SMSPXEIMAGES$) In DHCP (which is on a different server) I have the following options set (on 1 scope that I am testing this with) Option 60 = PXEClient Option 66 = 10.59.100.50 (IP of SCCM server) Option 67 = REMINST\Boot\x86\wdsnbp.com On my Core Switch I have IP Helper address which forward requests to the 2 DHCP servers. When I try and boot the client using PXE I get the error that says: proxydhcp did not reply to request on port 4011 Can anybody point me in the right direction as to what I have done wrong or missed?

We've just noticed that on selected servers our backup jobs are not running according to the schedule we have set. They appear to be around 30 minutes earlier or later than specified. For example: I have 4 DCs in 1 protection group set to backup the system state at 11:30pm everyday. The jobs are actually running at 12:00am the following day I have 2 seperate volumes of the same fileserver set to back up which should run at 7am, 11am and 4pm. One of the volumes is running this schedule while the other is running 6:30am, 11am, 4pm. They are in the same protection group. Here are some screenshots showing the discrepancy: 1: From the monitoring tab cleary shows the job started at 7:04:11 am - http://i55.tinypic.com/k3ocl.jpg 2: From the recovery tab showing that the only 3 points for 7th Jan are 6:28am, 11:02am and 4:01pm - http://i52.tinypic.com/jjl0ee.png The situation for the DCs is the same, monitoring tab shows the scheduled start time, recovery tab shows a different time. The DCs in question run W2K8 SP2 and the fileserver W2K3 R2 SP2. We are running DPM2010 and the agent versions are 3.0.7706.0 Any ideas why the jobs are running like this? Cheers Adam.

@bossman: It works if you put it in the C:\Windows also! Good shout!

Fixed! Turns out SIMS was looking for a copy of connect.ini in \\server\sims\WINDOWS, once i'd copied the connect.ini there it was happy. Then I discovered that it wasn't able to find the ExamsW.exe executable because it was looking in C:\Program Files\SIMS\SIMS.net but by default you are prompted to install SIMS in C:\Programs Files (x86)\SIMS\SIMS.net. Re-installed to C:\Program Files\SIMS\SIMS.net and it's happy again!

Since upgrading our 2 SIMS terminal servers to Windows Server 2008 R2 staff with normal user accounts are unable to run any of the "older modules" such as Exams Org on either of the servers. They get the error: Fault Code: 4257-7697-3000 Incorrect Connect.ini file : SIMS.Processes.Exception They can load and use SIMS perfectly fine so I am cofused about what exactly is incorrect with connect.ini and when I log onto the server as an administrator everything works as expected - so some sort of permission issue, but what?!?! The connect.ini in the C:\Programs Files (x86)\SIMS\SIMS.net dir is set to redirect to the root of our mapped drive where the connect.ini exists with all the correct settings. Staff have been given modify rights on the whole C:\Programs Files (x86)\SIMS\SIMS.net folder and connect.ini on the mapped drive - still it doesn't work. Capita's suggestion was to uninstall SIMS and .NET Framework from the server and re-install which I have done and it's made no difference - oddly enough the SIMS Infrastrucure application did not appear in the "unistall a program" list. Any suggestions on how to get this working.

Panic over! I'd also installed Culumative Update 2 for SQL 2008 SP" and this caused the problems. After uninstalling it all now works.

Hi, We've upgraded on SIMS/FMS server to 7.136/6.136 and set about upgrading our clients. On most machines after upgrading FMS we are now getting a General SQL Error: General SQL error. [Microsoft] SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [Microsoft][sql Native Client] An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [Microsoft][sql Native Client] Login timeout expired Alias: dbCheckLogin I've checked everything I can think of, firewalls are off on both server and client, fmsconnect.ini is correct, sever is accessible from the clients experencing the problem, checked the entry for the SIMS_FMS_DATABASE User DSN under ODBC which is correct and even rebooted the affected client as suggested in one KB article on SupportNet. When trying to login to SIMS after upgrading on these clients we are getting reason 0 errors. I've worked through the various fixes and nothing appears to make a difference The server is running SQL 2008 SP2 and yesterday I upgraded the OS from Windows Server 2008 SP2 x64 to Windows Server 2008 R2 as it is supported from the Autumn 2010 release - I'd upgraded to Autumn 2010 prior to the OS upgrade. My gut feeling is that the upgrade as done somthing to SQL and that the reason it no longer works, but what?

Phil, 1010-786014

We run the nightly export to Fronter and I have noticed that from September we are missing 16 of our registration groups - all Year 12 and Year 13. Years 7 to 11 are fine but the main difference between them are 7-11 are structured horizontally and 12-13 are strucutred vertically. I've logged a call with Fronter who said it was an MIS issue, logged a call with Capita who said it was a Fronter issue - i'm inclined to agree with Capita. Does anybody else have a similar setup in terms of mixed structures exporting to Fronter?

Yep. On your CAS Server, open IIS Manager and select the Default Web Site. On the right hand side, under actions, click bindings. On one of the http bindings I had our internal FQDN for OWA and removing this fixed the problem.

Upgraded to DPM2010 over the summer. Love it! No more intervention require when replicas become inconsistent or run out of space etc... If that happens DPM deals with it automatically, grows the volume (assuming you have told it to) and resolves the error itself. Run it on the same server as BE 2010 with no problems.

I've just discovered that when any of our users set OOF messages on their e-mail accounts those bound for external addresses are not being delivered. In message tracking on Exchange 2010 "550 Relaying not permitted (3.7)" is being reported presumably by our ISPs (Synetrix) SMTP server. Sending a standard reply to the address the OOF would have gone to works perfectly fine. I'm wondering, is this a problem their end or something I have missed during setting up Exchange 2010? Cheers Adam.

Not exactly the same error, but the same end result. Have you checked for host headers on the site bindings on the default website in IIS?

It was RTM

It was discovered through troubleshooting with MS. They didn't actually say it's not a supported config.

Ok.... I had a host header in the site bindings for the default web site in IIS. Not sure why or how that got there. Removing that, run iisreset from cmd prompt and it's now working again.

I have a call open with Microsoft so when/if I get an answer i'll stick it up here. Glad i'm not the only one

Yep all installed, although I had 5! I had to phone MS for this one: An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2 I didn't run it from an evelated cmd prompt. Just ran setup.exe. It appeared to install fine, no complaints, except for the missing hotfixes.

Upgraded to Exchange 2010 SP1 this morning and now it appears to have broken core functions within OWA. 1) I am now unable to delete messages (from any folder). I get this very helpful message: An unexpected error occurred and your request couldn't be handled. 2) I am unable to save changes to any options such as signatures, out of office, inbox rules etc.... Again, a very helpful message: Sorry! We're having trouble processing your request at the moment. Please try again later. I get these 2 errors in the application log whenever I try something above: WebHost failed to process a request. Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/30542218 Exception: System.ServiceModel.ServiceActivationException: The service '/EWS/exchange.asmx' cannot be activated due to an exception during compilation. The exception message is: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. Parameter name: item. ---> System.ArgumentException: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. Parameter name: item at System.ServiceModel.UriSchemeKeyedCollection.InsertItem(Int32 index, Uri item) at System.Collections.Generic.SynchronizedCollection`1.Add(T item) at System.ServiceModel.UriSchemeKeyedCollection..ctor(Uri[] addresses) at System.ServiceModel.ServiceHost..ctor(Type serviceType, Uri[] baseAddresses) at System.ServiceModel.Activation.ServiceHostFactory.CreateServiceHost(Type serviceType, Uri[] baseAddresses) at System.ServiceModel.Activation.ServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses) at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath) at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath) at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath) --- End of inner exception stack trace --- at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath) at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath) Process Name: w3wp Process ID: 4324 Outlook Web App couldn't connect Exchange Web Services due to a configuration error. Response code = "500". Has anybody else had any issues?

Having recently upgraded to Exchange 2010 an issue has been highlighted by some of our staff that searching is very slow and results are not displayed when searching using Outlook Web App. If you enter a search term and wait for the searching dialog box to apper, then click refresh, the results are displayed - but they never seem to appear on there own. Does anybody have any ides why this might be?

Fair point.... I'll leave it where it is.

Is it possible to do the same thing with FMS, have the mdf and ldf on seperate drives?

I've started to try out SIMS Remote Agent Installer but when I do it only lists workstations that are on the same domain as the server. The clients I want to deploy agents to are on a different domain. Is this by design or am I missing something? Cheers Adam.