I guess SQL doesn’t care about SIDs, so you likely would need to replace it.

 

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Radu Bogdan
Sent: Mittwoch, 25. September 2013 22:09
To: [email protected]
Subject: Re: [mssms] CU3 upgrade issues

 

Point taken Roland,

 

But in this situation is there a solution for this issue ?

 

 

From: Roland Janus <mailto:[email protected]>  

Sent: Wednesday, September 25, 2013 10:55 PM

To: [email protected] 

Subject: RE: [mssms] CU3 upgrade issues

 

Try to use groups whenever you can and have the accounts added to the group…

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Radu Bogdan
Sent: Mittwoch, 25. September 2013 21:33
To: [email protected]
Subject: Re: [mssms] CU3 upgrade issues

 

Mr. Stuart,

 

You are a genius !

 

Indeed this account was renamed a month ago, but not by me but by another 
domain admin. ( new name convention reasons )

 

In the SCCM console, in the Administrative Users I have the new renamed 
account, but in my SQL Server Management Studio, under Security-> Logins I have 
the old account...

 

Should I delete the old account from SQL and re-add the new one with the exact 
permissions on the SCCM DB ?

 

 

From: Stuart Watret <mailto:[email protected]>  

Sent: Wednesday, September 25, 2013 9:52 PM

To: mailto:[email protected] 

Subject: Re: [mssms] CU3 upgrade issues

 

I see what you did there. 

Probably unrelated but although the account is a domain admin is it the same 
account that installed the rest and particularly, has it ever been renamed? I.e 
same account but renamed at some time. 

Sent from a dog and bone. 


On 25 Sep 2013, at 19:19, "Mark Mears" <[email protected]> wrote:

The answer was that the service account DID have access to the file.

 


Thanks,

  _____  


 

Mark Mears

mailto:[email protected]%0d

Phone: (757) 945-2651

 

 <http://www.cireson.com/> <image001.png>


 

 <http://twitter.com/teamcireson> <image002.jpg>  Check out our System Center 
App Store:  <wlmailhtml:www.cireson.com/app-store> www.cireson.com/app-store

 


  _____  

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Radu Bogdan
Sent: Wednesday, September 25, 2013 2:13 PM
To: [email protected]
Subject: Re: [mssms] CU3 upgrade issues

 

Can you kindly offer me the answer please ?

 

Thank you.

 

 

From: Mark Mears <mailto:[email protected]>  

Sent: Wednesday, September 25, 2013 8:03 PM

To: [email protected] 

Subject: RE: [mssms] CU3 upgrade issues

 

I already know the answer to this but verify that the service account has 
security access to the file.

 


Thanks,

  _____  


 

Mark Mears

mailto:[email protected]%0d

Phone: (757) 945-2651

 

 <http://www.cireson.com/> <image001.png>


 

 <http://twitter.com/teamcireson> <image002.jpg>  Check out our System Center 
App Store:  <wlmailhtml:www.cireson.com/app-store> www.cireson.com/app-store

 


  _____  

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Radu Bogdan
Sent: Wednesday, September 25, 2013 1:01 PM
To: [email protected]
Subject: Re: [mssms] CU3 upgrade issues

 

Hello, 

 

Thank you for your reply.

 

I have it:

 

<image003.png>

 

Any hints ?

 

 

 

From: Mark Mears <mailto:[email protected]>  

Sent: Wednesday, September 25, 2013 6:58 PM

To: [email protected] 

Subject: RE: [mssms] CU3 upgrade issues

 

The log file is barking because it cannot locate a file.  Can you verify that 
the file [[SMS_ROOT]]\bin\x64\MessageHandlerService.dll exists?

 

CREATE ASSEMBLY failed because it could not read from the physical file 
'[[SMS_ROOT]]\bin\x64\MessageHandlerService.dll': 50(The request is not 
supported.).

 

 


Thanks,

  _____  


 

Mark Mears

mailto:[email protected]%0d

Phone: (757) 945-2651

 

 <http://www.cireson.com/> <image001.png>


 

 <http://twitter.com/teamcireson> <image002.jpg>  Check out our System Center 
App Store:  <wlmailhtml:www.cireson.com/app-store> www.cireson.com/app-store

 


  _____  

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Bogdan Radu
Sent: Wednesday, September 25, 2013 11:37 AM
To: [email protected]
Subject: [mssms] CU3 upgrade issues

 

Hello,

 

Upgrade SCCM 2012 SP1 to CU3.

 

I receive a warning on “Perform Database Update” like in here:

 

http://infoworks.tv/2013/09/02/configuration-manager-2012-sp1-cu2-installation-warning-perform-database-update/

 

 

Ok so I run the “Update.sql” script manually from the SQL Server ( 2008 R2 SP1 
).

 

I receive the following:

 

(1 row(s) affected)

Msg 6502, Level 16, State 7, Line 2

CREATE ASSEMBLY failed because it could not read from the physical file 
'[[SMS_ROOT]]\bin\x64\MessageHandlerService.dll': 50(The request is not 
supported.).

Msg 6528, Level 16, State 1, Procedure fnCompressData, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX.

Msg 6528, Level 16, State 1, Procedure fnConvertBase64StringToBinary, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX’.

Msg 6528, Level 16, State 1, Procedure fnConvertBinaryToBase64String, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX’.

Msg 6528, Level 16, State 1, Procedure fnDecodeStringWithBOM, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure fnDecompressData, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure fnDRSGetDataHeader, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure fnEncodeUTF8, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure fnEscapeSpecialCharactersForXml, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure fnUnescapeSpecialCharactersForXml, Line 
10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure spDRSActivation, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure spDRSDeserializeData, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure spDRSSerializeQuery, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure spModifyGlobalTable, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

Msg 6528, Level 16, State 1, Procedure spUpdateMasterTableSchema, Line 10

Assembly 'MessageHandlerService' was not found in the SQL catalog of database 
'CM_XXX'.

 

 

 

 

 

 

 

 

 

 




Reply via email to