Advertisements
SQL
-
-
July 30, 2012After moving the System Center 2012 Configuration Manager (SCCM2012) SQL Site Database to another drive, creating a new Software Update package or a new application fail Symptoms After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update group, Software Update package, or creating a new application fails and errors similar to the following are logged in the SMSProv.log file: *** *** Unknown SQL Error! SMS Provider 14-03-2012 07:56:47 2016 (0x07E0) *~*~*** Unknown SQL Error! ThreadID : 2016 , DbError: 50000 , Sev: 16~*~* SMS Provider 14-03-2012 07:56:47 2016 (0x07E0) *** [24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state SMS Provider 14-03-2012 07:56:48 2016 (0x07E0) *~*~[24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state *** Unknown SQL Error! ThreadID : 2016 , DbError: 0 , Sev: 0~*~* SMS Provider 14-03-2012 07:56:48 2016 (0x07E0) SQL Profiler provides the following additional details: An error occurred in the Microsoft .NET Framework while trying to load assembly id 65539. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: System.IO.FileLoadException: Could not load file or assembly ‘cryptoutility, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A) System.IO.FileLoadException: at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) Cause This can occur if the SQL Site Database MDF and LDF files are moved to a different drive. For example, if originally the Configuration Manager Site Database was created on C:Program filesMSSQL serverdata but then later the MDF and...
-
April 11, 20121. Login on to the server you want to change the name of 2. Run this in Microsoft SQL Server Management Studio 3. Click on Create New Query 4. Enter this code to get the existing name. select @@servername 5. After code is entered click the red exclamation point to execute 6. The current name will be returned. 7. Next enter the following text filling in the appropriate information for you environment. sp_dropserver 'old_name' go sp_addserver 'new_name','local' go 8. After code is entered click the red exclamation point to execute 9. Now close Microsoft SQL Server Management Studio 10. Run the command prompt Administrator and run the following two commands net stop mssqlserver net start mssqlserver 11. Now reopen Microsoft SQL Server Management Studio and rerun select @@servername 12. Make sure the name matches the ‘new_name’
-
January 10, 2010Microsoft SQL Memory Leak work around. Microsoft SQL is a huge memory resource consumer there is no fix besides add more memory but there is a work around Microsoft provides 1.Log into the SQL Server using SQL Server Management Studio 2.Right click on the server go to properties 3.Click on the memory tab 4.Now the calculation is done in Megabytes 1024 MB is a gig 5.Subtract the system ram you want to leave free from your over all RAM. 6.I would leave at least 4 gigs of RAM free for the Operating System if possible. 7.The final answer is the number you type into the box that says “Maximum Server Memory (in MB)” 8.Click OK