09 July 2019
Unknown SQL Error! in SMSProv.log
I was at a customer who could not start ConfigMgr console on the site server after an CB update.
In SMSProv.log following messages was thrown:
*** *** Unknown SQL Error!
*~*~*** Unknown SQL Error! ThreadID xxxx, DbError: 50000, Sev: 16~*~*
Results returned: 0 of -1
It turned out that the customer has performed a CB update. During the "Prerequisite Check" they had a warning on SQL server level.
After the update - that went well - they looked at the SQL server.
At some point someone has tried to install a service pack, which has only updated some (?) SQL components, leaving others in current state.
They tried to install the service pack again, but they could not, because the sql was already updated...
They detached the databases, uninstalled and installed the sql server, updated it and attached the databases again.
The ConfigMgr console could not start up...
I did the ConfigMgr Reset, checked the right on the SQL server and databases - all fine, but still the ConfigMgr console didn't start.
Luckily I found a post that stated that ConfigMgr requires SA to be owner of the database.
When you do an attach, the user doing this will become the owner.
I ran EXEC sp_helpdb and found the userid for the person who attached the databases as Owner.
To change the owner, I ran:
USE
GO
EXEC sp_changedbowner 'sa'
After this, I could start up the ConfigMgr console again.
In SMSProv.log following messages was thrown:
*** *** Unknown SQL Error!
*~*~*** Unknown SQL Error! ThreadID xxxx, DbError: 50000, Sev: 16~*~*
Results returned: 0 of -1
It turned out that the customer has performed a CB update. During the "Prerequisite Check" they had a warning on SQL server level.
After the update - that went well - they looked at the SQL server.
At some point someone has tried to install a service pack, which has only updated some (?) SQL components, leaving others in current state.
They tried to install the service pack again, but they could not, because the sql was already updated...
They detached the databases, uninstalled and installed the sql server, updated it and attached the databases again.
The ConfigMgr console could not start up...
I did the ConfigMgr Reset, checked the right on the SQL server and databases - all fine, but still the ConfigMgr console didn't start.
Luckily I found a post that stated that ConfigMgr requires SA to be owner of the database.
When you do an attach, the user doing this will become the owner.
I ran EXEC sp_helpdb and found the userid for the person who attached the databases as Owner.
To change the owner, I ran:
USE
GO
EXEC sp_changedbowner 'sa'
After this, I could start up the ConfigMgr console again.
07 May 2019
19 February 2019
Fix iPhone battery problem
A couple of days ago my iPhone 6s suddenly started loosing power. Rapidly it went from 80% to 1% (but 1% could last very long time).
It was fast to charge up, but again it rapidly lost power and went to 1%.
Since I could use the phone for a long time when it stated 1% I didn't think it was the battery that was the problem.
I did some (a lot) search and found this advice that could help, and it was much easier than resetting the phone and much cheaper than a new battery.
The article I found, was on a Danish part of "ON X" and it was started in 2012 but has comments right up till now from greatfull readers that has been saved by the tip:
Shutdown the iPhone
Remove SIM card
Power On iPhone and accept that there are no sim card inserted
Shutdown the iPhone
Insert SIM card
Power On iPhone
And - voila - problem is gone (ok, some had do to do it twice)
It was fast to charge up, but again it rapidly lost power and went to 1%.
Since I could use the phone for a long time when it stated 1% I didn't think it was the battery that was the problem.
I did some (a lot) search and found this advice that could help, and it was much easier than resetting the phone and much cheaper than a new battery.
The article I found, was on a Danish part of "ON X" and it was started in 2012 but has comments right up till now from greatfull readers that has been saved by the tip:
Shutdown the iPhone
Remove SIM card
Power On iPhone and accept that there are no sim card inserted
Shutdown the iPhone
Insert SIM card
Power On iPhone
And - voila - problem is gone (ok, some had do to do it twice)
Subscribe to:
Posts (Atom)