Home > Event Id > Event Id 17137

Event Id 17137


Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? I do not have any problem so far. WhenAuto Closeis on for a database, SQL closes thedatabase when the last connection closes. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=111476&SiteID=1   Saturday, July 07, 2007 12:42 PM Reply | Quote 0 Sign in to vote Hi,I am having the same problem it seems, is this a serious issue? Check This Out

Math / Science Solar Technology Advertise Here 658 members asked questions and received personalized solutions in the past 7 days. Thanks for everything! However, I can get to those settings using the SQL Server 2005 Surface Area tool, but after restarting the WID (Microsoft#ssee) instance the remote connections properties reset back to Local Connections If you have already registered your product then please contact Customer Service directly for further assistance at [email protected]

Event Id 17137 From Source Mssql$microsoft##ssee Cannot Be Found

TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. SharePoint > SharePoint Legacy Versions - General Discussions and Questions Question 0 Sign in to vote Hi, I started using Sharepoint service 3.0. EventID.Net From a newsgroup post: "These repeated "starting up" messages seem to indicate that you have "Auto-Close" enabled for one or more databases.

read more... Friday, July 06, 2007 10:43 AM Reply | Quote 0 Sign in to vote Hi, Thank you for replying.   I checked it, but I could not find logs under that The properties of the object is not existing or can't be accessed because of insufficient rights. (Microsoft.SqlServer.Express.Smo) Strange is, that I see different database in the Management studio: 1 SharePoint_AdminContent_081c10da-430b-4a95-9867-a1d02f835b22 The Microsoft#ssee instance isnt visible in the SQL Server Configuration Manager under "SQL Server 2005 Network Configuration".

Either the component that raises this event is not installed on your local computer or the installation is corrupted. Adfsartifactstore Question has a verified solution. Continue × Register as SonicWALL User Sorry, we are having issues processing your request. https://www.interactivewebs.com/blog/index.php/crm/event-id-17137-from-source-mssqlmicrosoftssee/ Continue × Support Forms Under Maintenance Submitting forms on the support site are temporary unavailable for schedule maintenance.

It is possible that updates have been made to the original version after this document was translated and published. OK × Welcome to Support You can find online support help for*product* on an affiliate support site. x 18 Private comment: Subscribers only. Event ID: 17137 Source: MSSQL$SQLEXPRESS Source: MSSQL$SQLEXPRESS Type: Information Description:Starting up database "".

  1. Can you help me with how I connect to the server-name\microsoft##ssee instance using the SQL express management studio ?
  2. Tuesday, April 17, 2012 4:36 PM Reply | Quote 0 Sign in to vote Thank you!
  3. Friday, July 06, 2007 4:46 PM Reply | Quote 0 Sign in to vote   We have 2GB RAM on the server.
  4. Article:000006789 Publish: Article URL:http://www.veritas.com/docs/000006789 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in
  5. No Yes Did this article save you the trouble of contacting technical support?
  6. Either the component that raises this event is not installed on your local computer or the installation is corrupted.
  7. Regsrds Chris Friday, November 26, 2010 11:38 AM Reply | Quote 0 Sign in to vote I was getting the above error message The description for Event ID 17137 from source
  8. Thursday, November 25, 2010 10:56 AM Reply | Quote 0 Sign in to vote Hi, Well my Companyweb is working, but don't ask me why.
  9. Hope this helps.


Source: MSSQL$SQLEXPRESS Type: Information Description:Starting up database "". 2 Comments for event id 17137 from source MSSQL$SQLEXPRESS Source: MSSQLSERVER Type: Information Description:Starting up database . 1 Comment for event id PRTG is easy to set up &use. Event Id 17137 From Source Mssql$microsoft##ssee Cannot Be Found Reply ↓ Ronald Hine on March 13, 2015 at 12:33 pm said: Big thumbs up on that solution, worked a treat. Sql Server Auto Close Comments: EventID.Net See the comments for the same event id source MSSQL$SQLEXPRESS.

In the eventlog I have hunderets of entrys with ID 5084, 8128, 17137 and 26048. his comment is here It allows you to jump in and be sure that SQL is running as it should. Thanks again. I only see the SBSMONITORING instance.

PRTG is easy to set up &use. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking Privacy statement  © 2017 Microsoft. this contact form Event ID 17137 Source: MSSQL$DESKTOPAUTHORITY Starting up database 'DAConfiguration or DAReporting'.

This is a topic that greatly interests me and so I decided to produce a video about it. Now you can use SQL Server Management Studio to connect to your database instance, and change the “Auto close” option on your Sharepoint databases. Was this article helpful? [Select Rating] Request or Create a KB Article » × Request a topic for a future Knowledge Base Article Request a topic for a future Knowledge Base

All rights reserved.

The following information is part of the event: WSS_Content.Data:0000: f1 42 00 00 0a 00 00 00   ñB......0008: 1e 00 00 00 46 00 49 00   ....F.I.0010: 4c 00 45 00 English: Request a translation of the event description in plain English. You can install or repair the component on the local computer. Join Now For immediate help use Live now!

Search Main menu Skip to primary content HomeAbout InteractiveWebs InteractiveWebs Home Post navigation ← Previous Next → Event ID 17137 from source MSSQL$MICROSOFT##SSEE Posted on June 27, 2012 by InteractiveWebs Reply ↓ InteractiveWebs on August 21, 2014 at 8:14 am said: Frankly, you are best installing the management studio (big name for a small program) on the server. You may also refer to the English Version of this knowledge base article for up-to-date information. navigate here Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended

Login here! I did not reboot the system or stop/start any service, but as I had no connect to my Exchange OWA I saw in the IIS-Manger that all pages where down (stopped). OK × Featured Content What's new in 10.0 Anti-virus exclusions How licenses are counted Upgrade FAQ's Self Service Tools Knowledge Base My Account Product Support Professional Services Software Downloads Technical Documentations OK × Contact Support Your account is currently being set up.

Open SQL Management Studio and connect to the instance where the databases are stored2.