Input Not Supported

I was in my mac mini playing with the display settings and I clicked on one that was way to big for my monitor. Now its not coming up at all. I can see the screen when it boots up, however when it gets to the OS, the screen goes to a blank black screen and says "Input Not Supported" Please Help. I just got this 4 days ago.

I believe the easiest way to recover from this is to boot into safe mode.
http://docs.info.apple.com/article.html?artnum=107393
That should cause the mini to boot in a lower, default resolution. Once you have a useable image, go into display prefs and set the resolution back to the desired one you were using before and reboot.

Similar Messages

DVI to VGA adapter, monitor says "input not supported"

I have just received my MBP yesterday and, when I attempted to attach it via DVI to VGA adapter to my Acer AL2016W flat panel LCD, the monitor told me "input not supported". I was under the impression VGA is VGA is VGA. Perhaps I am mistaken. There is no DVI port on this monitor so I am, essentially, screwed ATM unless I purchase yet another monitor - this one is less than a year old. I require my MBP to be attached to an external monitor due to a disability, and am not sure what to do. I don't believe it to be an isolated issue, especially after viewing some of the other posts about the graphics card being an issue as well. I wish Apple would come forward with a resolution. I realize this issue has probably been posted somewhere already, however I am unable to sift through all the posts due to the aforementioned disability and inability to attach to external monitor. I just can't sit here for that long, so I offer my apologies.

First off, are you connecting in the proper sequence? That is:
1. MBP and monitor powered on
2. connect monitor's VGA cable to the DVI-to-VGA adapter
3. connect DVI-to-VGA adapter to the MBP's DVI port
In that way, the MBP should autodetect the monitor and set the resolution appropriately. Else, the output resolution of the MBP may not suit the monitor, and the monitor will give a "not supported" error.
As a side note, have you considered the options in System Preferences > Universal Access? Options include Zoom, VoiceOver (spoken screen selections), making the cursor larger, and other enhancements for the visually impaired.
Hope this helps...

External display and "clam shell" closed lid mode = "Input Not Supported"

I have an Acer AL2016W 20" monitor hooked up to my again Powerbook due to it having a cracked screen. It is working just fine right now, in 1680x1050, when the screen is open. Citing this article,
http://support.apple.com/kb/HT3131
I should be able to close it and have it working as well. When I do close it then wake it, I just get a "Input Not Supported" message on the monitor. Any help?

I'm still puzzled at why it the screen is activated when the lid is closed and woken with an external USB device
That's rather puzzling as the display should not work if the lid is closed. If you have an external drive you're able to install a clean copy of Mac OS X to and boot from you can see if the issue persist there. If it does then it's most likely a hardware issue and you should contact AppleCare. If it doesn't then it has something to do with either your software installation else some utility you've installed.

Problems with new display, "Input not supported"

So, I just got myself a new LCD screen (Acer AL2016WCbd) for my G4 (DP 1Ghz Quicksilver 2002 w/ 10.5 installed). The monitor seems to work alright and everything with my Windows box, but whenever I try to use it with my G4 the monitor goes black, flashes an error box saying "Input not supported," and then goes to sleep. It does show the boot screen... the gray background and Apple logo... but goes black after that.
I've tried rebooting, resetting the PMU, tried booting in Single User and Verbose mode, tried hooking the G4 up to another monitor and lowering the resolution to 800x600 @ 75Hz and then reconnecting the Acer, but no dice.
My only other ideas are to try hooking it up over DVI instead of VGA (though I'd need to get an adapter for that); playing around with a few different things in target disk mode by hooking it up to my laptop (which I don't currently have); and trying to boot from my Leopard install disk (when I find it). Might any of these things do any good? Is there anything else I haven't thought of? Or am I just wasting my time?

OK, so I can get the display working if I first boot up with another display, set the resolution to whatever I want it to be, then hotswap in the Acer that's been giving me the problems. But once I restart my computer I have to go through the whole process again. Either the tower isn't picking up on the display profile from the monitor or the monitor just isn't sending it to the tower.
My question now is: is there a way to for me to lock the resolution and refresh rate, so it always outputs at, say, 1680x1050 at 60Hz? Both Newegg and Acer have been giving me all kinds of (excuse me here) sh** about how they can't help me, so I really don't want to deal with them anymore by having to return/exchange the monitor or get it serviced. I mean, I know the thing works and I know the resolution I want it to run at. I just want to be able to lock it so Leopard doesn't revert to some unsupported output every time I reboot.

I have acer al1916w and i have a problem message that say input not supported help

i have acer al1916w and i have a problem message that say input not supported help

under windows 7 - 8.1right click on your desktop and choose screen resolution set a very basic resolution like 1280x1024 @ 60Hz (frequency can be set under advanced options); you need to have a working monitor to set this and then reboot connecting your al1916w. if it still gives you that message, can be a bad cable or some hardware monitor issue.

Acer AL 707: "Input not supported" - What can I do?

Hello everybody!
I've bought a new Mac mini and I wanted to change the screen resolution and suddenly, the screen got black and a message "Input not supported" appeared. What can I do? I'm totally helpless.

Reset the pram
This should erase your monitor preference.

Mac mini input not supported

After I power up my mac main with 10.4.1 os I type in my password, then the screen goes black and says " input not supported"

Try a safe boot.
     Shutdown your machine. Hold down the shift key. Poweron. Wait awhile; wait awhile while you harddrive
     is being checked.
     http://support.apple.com/kb/ht1455

Intermittent "Input Not Supported"

A few days ago picked up a Mac Mini to make into a video server. I have it currently hooked up to my old PC's LCD monitor (17" Envision cheapy from when LCDs first became affordable 5 or so years ago) while I work on converting my DVD collection to it.
A number of times, when the monitor comes back on (after it times out), it will show as "input not supported". I turn the monitor's power off and back on and eventually it will bring the display back. A couple times it was somewhat scrambled along the bottom edge also.
I have the display settings to a resolution that works with this monitor and OSX automatically detects the display (EN-7100e).
I haven't used this monitor much recently, but when running on the old PC didn't have any issues with it. Would OSX be confusing it possibly when awaking the monitor? Have others experienced this issue?

Now that's an interesting data point. The mere act of viewing the mini's screen from a remote client should not cause any change in the video output of the mini. There is definitely something strange going on.
Here's a question: if you cold boot the mini while it is connected to the Envision, but the Envision is powered off, and if you then remotely connect to the mini from the MBP with the Envision still off, what screen resolution is the mini running at in that case? Also, if you look at Display's preferences on the mini from the MBP (Envision still off), does it indicated the Envision is attached or not?

10.7.3 external monitor "input not supported"

I have an external monitor connected with the Aplle VGA adaptor to my MBP.
It has been working fine for the last year.
Today I installed 10.7.3
And now I get the message "Input Not Supported" on the external display.
Not impressed.
Any ideas or do I have to roll back this update.
Cheers.

OK now it gets silly.
I have also had a problem, since I instaled Lion, that when I open my MBP the screen is black and no amount of encouragement will bring it to life.
So, I have to switch on my external monitor. My deskptop thern appears on the externam monitor, so I select "Detect Displays" from the menu bar and, kazam, my MBP screen comes to life and the desktop moves there.
It only remains for me to switch off the external monitor and wait for Apple to provide a fix.
Now, remember my current problem, in that the external monitor wil not work and shows "input not supported".
So today I opened my MBP and sadness, the screen is BLACK. So I switched on my external monitor and WAHEY! it worked and the desktop appeared on the external monitor.
Excited at the prospect that my problem had somehow magilcally fixed itself overnight, I selected "Detect Displays" and my MBP screen duly appeared and the desktop meved there.
The external monitor then stopped working and showed the message "Input Not Supported"
I also have a related VNC problem that is still outstanding, so I think it is fair to say that there are several issues around external monitors with Lion.

Roving error message on black screen at start up "Input not supported)

HP Pavilion media center a1547c, running XP. Changed the resolution because the icons appeared larger and the screen went black with a roving error message "Attention: Input not supported" message box is white with grey stripes top and bottom. On restarting, WindowsXP logo comes up, then error message appears but I can hear the Windows "chimes". Anyone?

Start Windows XP in safe mode. Press the power button and then begin tapping the F8 key before Windows boots up. Choose Safe Mode with command prompt. While in safe mode, start system restore by typing rstrui.exe and pressing enter. Choose a restore point dated before before the initial problem began. This may resolve the issue. If it does, fantastic. If not, then continue with the troubleshooting as described below.
When Windows restarts consider two troubleshooting scenarios to isolate the issue. What you need to know is whether the problem lies with the PC's video output of the LCD display.
1) connect a different display to the PC and log into Windows to see if the windows desktop is normal.
2 )install a low powered (inexpensive and less than 1GB VRAM) PCI Express x16 video card. You need to see if that corrects the display issue with the original display connected. That will show you if the motherboard's video output is the issue.
Don't forget to post your result here in your thread.
Best regards,
erico
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Rage 128 Pro and HP Monitor= 'Input Not Supported'. Need help.

I recently purchased this monitor for my Mac G4 (Digital audio model with Rage 128 Pro);
http://www.macmall.com/macmall/shop/detail.asp?dpno=7246171&Redir=1&description= HP-Smart%20Buy%20w19%2019-inch%20LCD%20Widescreen%20Flat%20Panel%20Monitor-Monit ors
When I power up the Mac I can see the apple logo as OSX starts to boot but soon thereafter I get a black screen with a little floating window that says, 'Input Not Supported'.
What does this mean in technical terms and do I need to return the monitor?
Thanks.

Hi-
The monitor is telling you that the input being received is not supported. This is because the rage 128 is too weak a graphics card to drive the HP Monitor ( or any LCD over 17" for that matter).
You will need a better graphics card to run the display.
As for which graphics card, basically, most any 4x AGP Mac compatible card +other than+ the Rage 128 (or Pro) will work to drive the monitor.
http://hardcoremac.stores.yahoo.net/memory3.html
http://www.welovemacs.com/agpvideocards.html
http://eshop.macsales.com/shop/video/hardware/

Help!!! Installed Sound Card driver does not support Direct Sound input

I have just installed Premier Pro CS3 on a brand new PC. I am a new user and I am receiving a message "The installed sound card driver does not support direct sound input".
PC is a 3 GHZ Intel Duo
4 G RAM
2 x 500 G HD
Windows Home Vista Preminum
I am sure it is a simple fix and really appreciate any one given me the time or guidance to help get me started.
Many Thanks
Brendan

Thanks Harm for the prompt reply, nice one!
Sound Card is a "Realtek High Definition Audio"
Driver Version 6.0.1.5408
It was shipped with this Dell PC.
I checked the driver was up to date etc. So not sure what to do now.
Cheers

Satellite A210-131 sound driver does not support DirectSound input

Starting Premiere Pro CS3 , an error message appears:
- "Der zurzeit installierte Soundkartentreiber unterstuetzt keine DirectSound-Eingaenge" Es ist keine Audioaufnahme moeglich".
- "The installed sound card driver does not support the DirectSound input. The Sound recording is not possible"
Please help me to find a working driver. Operating system is Windows Visat Ulimate.
Thank you
Siegwin

Hi
In my personal knowledge the DirectSound is an addition to Microsoft's DirectX system. It should be included in the DirectX.
Please check if you have installed the newest version of DirectX 9C.
Furthermore I would recommend updating the sound driver. On the Toshiba page you could find the latest two versions of Realtek sound dirver;
- 6.0.1.5374
- 6.0.1.5406
If both will not support the DirectSound input try another one from the Realtek homepage.
The chip is called Realtek ALC268

Does the later 2009 MacBook support the Apple DVI to Video Adapter (s-video). I want to connect it to an old tv which does not support HDMI. Any suggestions?

I have a late 2009 MacBook which I want to connect to an old LG tv. The tv does not support HDMI it only has the (red, while, and yellow) ports. Sorry I dunno the exact name for it.
So I was thinking of using the Apple Mini DVI to Video Adapter (s-video), link below...
http://store.apple.com/Catalog/dk/Images/M9319_screen.jpg
But I'm afraid that the MacBook might not support the adapter.
Can anyone give me a solution for this? Is there an alternative way of doing this? I'm kinda new to apple display adapters.

The Late 2009 model 6,1 has a Mini DisplayPort not the Mini-DVI. To see which model you have go to the Apple in the upper left corner and select About This Mac, then click on More Info. When the System Profiler comes up check the Model Identifier.
Composite is the name for the red, white and yellow RCA plugs on your TV or red, white and S-Video plugs. If you want to use the Composite input on your TV there’s no Mini DisplayPort to Composite. You’ll have to get a Mini DisplayPort to VGA adapter http://www.amazon.com/s/ref=nb_sb_ss_i_1_19?url=search-alias%3Delectronics&field -keywords=mini+displayport+to+vga&sprefix=mini+Displayport+to and a VGA Adapter to TV S-Video RCA Out Cable for PC Video. http://www.amazon.com/VGA-Adapter-S-Video-Cable-Video/dp/B000Y7T5UU/ref=sr_1_7?s =electronics&ie=UTF8&qid=1316369974&sr=1-7
Only the Yellow plug or the S-Video plug for video will work. For sound you'll also need audio cables to the TV using a 3.5mm stereo headphone jack to RCA sound plugs. You attach it from the headphone jack of your MacBook to the appropriate input plugs on your TV http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=min i-dvi&x=9&y=13#/ref=nb_sb_ss_i_2_19?url=search-alias%3Daps&field-keywords=macboo k+audio+cable&sprefix=macbook+audio+cable&rh=i%3Aaps%2Ck%3Amacbook+audio+cable

SSRS in SharePoint Mode: Reporting Services scale-out deployment is not supported in this edition of Reporting Services [not true]

Hello,
We are experiencing some issues with SharePoint 2013 which is driving me insane.
We have a deployment with two SQL Servers (HA groups) and four SharePoint servers: 2 Application servers, and 2 Web FrontEnd servers.
We installed SSRS for SharePoint in both application servers. The disc I have used is the MSDN image of SQL Enterprise 2012 w/ SP2.
ISO name: en_sql_server_2012_enterprise_edition_with_service_pack_2_x64_dvd_4685849.iso
MD5: 003e14c55fa648ad15f8be1e2439bd06
The installation completes without any problems. We can start the SSRS SharePoint Service in the first application server without any issues. However when we try to start the second one, we get the following error:
Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the sql reporting services service in the farm. The SQL Server Reporting Services cannot be started on
this server unless it is stopped on all other servers in the farm.
Now I am at a loss here. As I mentioned, we have used an image of SQL Server Enterprise. This is the same image we used on other environment, which worked as expected (we got no such error).
I have included the text related to the correlation error from the SP logs below.
Has anyone ever seen this issue before? Very, very strange!
Regards,
P.
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=9.742 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 6t8h High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.23, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Web Controls 88wu High [Forced due to logging gap, Original Level: Verbose] SPGridView.OnRowCreated() - Row.RowType={0}, .RowState={1}, .RowIndex={2}, .DataItemIndex={3} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General af4yd High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.28, Original Level: Verbose] TenantAppEtag record requested but there is no sitesubscription or tenantId for site {0} so we will use the WebApp Id for the cache. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.43 OWSTIMER.EXE (0x1F10) 0x0B40 SharePoint Foundation Health abire Medium Failed to Sql Query data XEvent collector on sql-01. The error is Object reference not set to an instance of an object.
01/29/2015 14:13:26.51 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 7034 Critical An attempt to start/stop instance of service Microsoft SQL Server Reporting Services Shared Service on server SPAP-01 did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.40, Original Level: Verbose] SQL connection time: 0.0821 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88b9 High [Forced due to logging gap, Original Level: Verbose] Determining if the current user is a SharePoint Farm Administrator 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ReportingWebServiceInstance. Version: 1118292 Ensure: False, HashCode: 52212853, Id: 5a4058b9-2ecd-421e-b9ae-818bbc57c8c6, Stack: at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.57, Original Level: Verbose] SQL connection time: 0.0965 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88ch High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.84, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 8nca Medium Application error when access /_admin/Server.aspx, Error=Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.87 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Runtime tkau Unexpected System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.89 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,2 agb9s,9 b4ly,309 8xqz,331 8nca,15 tkau,8 ajlz0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48)). Execution Time=712.2145 6f83e49c-cc03-d049-90f4-81439b542cf8

Hi Wynn,
I appreciate your attempt to address my concerns, but even your reply seems to ignore the fact that I have not only provided the name of the ISO, but the MD5 checksum of the ISO as well. Also this is the first time I am being asked to double-check the version
of SSRS. The first reply I got to my query simply disregarded the version mismatch.
As per your request, I have checked under the folder you have specified (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices\LogFiles), but unfortunately there are no files under this folder in neither of my two application
servers.
We only have logfiles under C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS
Is there a way I can turn those logs on?
In the meantime, we run the SQL Server Discovery tool and I have attached the summary for you to see that it finds the Enterprise Edition of SQL Server:
Final result: Passed
Exit code (Decimal): 0
Start time: 2015-01-29 15:17:44
End time: 2015-01-29 15:17:56
Requested action: RunDiscovery
Machine Properties:
Machine name: SP-AP-02
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 Reporting Services - SharePoint 11.2.5058.0 No Yes
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation edition:
User Input Settings:
ACTION: RunDiscovery
CONFIGURATIONFILE:
ENU: true
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
QUIET: false
QUIETSIMPLE: false
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150129_151743\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
The \Setup Bootstrap\Log folder also has several log files that indicates the version of SQL Server that has been installed. For instance here is an entry of the Detail.txt file:
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : CreateSKUCookie succeeded, new checksum is 195 bytes.
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : Updated skuCheckSumInfo -> daysLeft=0 sqlEdition='ENTERPRISE' (0x6B9471A8) fileTimeInstalled=0 timeBombValue=0 editionType='Enterprise Edition' edition='Enterprise Edition' writeEditionStrings='True' checkSum=195bytes
(01) 2015-01-28 19:10:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
I hope this help while we don't have any logfiles in the folder you asked me to look into. Please advise me as in how to proceed if logfiles must be generated.
Regards,
P.

Input Not Supported

Similar Messages

Maybe you are looking for