Original post: https://blogs.technet.microsoft.com/sbs/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1/
Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.
The Following errors may be found in the server application log:
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation Search
Event ID: 70
Task Category: Gatherer
The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.
Log Name: Application
Event ID: 521
The backup operation that started at ‘?2011?-?07?-?06T02:12:07.198000000Z’ has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code ‘2155348129’. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
You can also run the following commands to determine if you need to complete the update process with PSCONFIG:
- Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
- Once the shell opens, type the following command followed by enter:
If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.
In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.
We have problem updating our Fujitsu S700 and S720 they are stucked in OS Version Elux RP 4.11.5-1, when we tried to update the OS to version 5 we getting the error message
Update failed: bad flash size
detailed log says:
-> failed, image size (502698 blocks) will exceed media size (453848 blocks)
Update terminated with error (err=-2, 291064 blocks free, 24343 files free)
Update checked (duration: 0 s, 291064 blocks free, 24343 files free, 0 bytes received, 0 bytes/s)
the client tell that it have a 1,8GB flash, but a system partition is only 453 MB.
the solution for us was to create a mini base image of the eLux 5.6 with minimum of packages, so that it could fit under the 450 MB volume, and then when it have completed successfully, we then could flash the full image to the device
When you get
Client Excluded: MACAddress:2c:be:08:f5:14:d6 Base Radio MAC :2c:d0:2d:91:54:86 Slot: 1 User Name: unknown Ip Address: unknown Reason:Attempted to use IP Address assigned to another device. ReasonCode: 3
you can debug the already used ip by enable dhcp debuging og the wlc controller
you can enable debuging by using the following command
debug dhcp message enable
you can look for the event
*DHCP Socket Task: Oct 11 09:11:56.591: 2c:be:08:f5:14:d6 DHCP option: requested ip = 10.16.0.254
then you know that the ip that is already in use is 10.16.0.254, and you can exclude it on the dhcp server
Dele brugt til at gøre min CR-10S mere lydsvag:
Creality CR-10S: https://3dstore.dk/shop/3d-printer/creality-cr-10s/
Steppermotor dæmpere: https://3dstore.dk/shop/tilbehoer/reservedele/creality-3d/nema-17-vibration-damper/
Bagblæser: orginal blæseren er 40X40X20, jeg har valgt at skifte den til denne lydsvage 60x60x25 fra noctua, http://noctua.at/en/nf-a6x25-flx sammen med denne adaptor: https://www.thingiverse.com/thing:2463339
PSU: har jeg skiftet til denne: Gelid Silent 6 (ebay link: http://www.ebay.com/itm/2-x-Pack-of-Gelid-Solutions-Silent-6-Quiet-Case-Fans-60mm-3200rpm-16-CFM/)
Bundkort: Noiseblocker BlackSilent Fan XS1 (ebay link: http://www.ebay.com/itm/Noiseblocker-BlackSilent-Fan-XS1-50mm-Lüfter-ITR-XS-1/)
Hotend: Noctua nf-a4x10-flx http://noctua.at/en/nf-a4x10-flx
ved brug af denne adaptor: https://www.thingiverse.com/thing:2522678
Pla: Noctua nf-a4x20-flx http://noctua.at/en/nf-a4x20-flx
ialt er følgende blæsere blevet brugt til projektet:
1x 60x60x25 (Noctua nf-a6x25-flx)
1x 50x50x10 (Noiseblocker BlackSilent Fan XS1)
1x 60x60x15 (Gelid Silent 6)
1x 40x40x10 (Noctua nf-a4x10-flx)
1x 40x40x20 (Noctua nf-a4x20-flx)
2x Nema 17 steppermotor dæmpere (på X & Y akserne)
Raspberry Pi 3: power off usb ports from shell
echo '1-1' |sudo tee /sys/bus/usb/drivers/usb/unbind
echo '1-1' |sudo tee /sys/bus/usb/drivers/usb/bind
Cisco wlc2504 lag with SG300
ssh to SG300
interface range GigabitEthernet x-y
channel-group 1 mode on
Error 1918, System Error Code 126, When Installing MySQL ODBC Driver 5.3 x86 (Link) on a Server 2016 64 bit
the solution was to install Visual C++ Redistributable Packages for Visual Studio 2013 X86: Link
Web Platform installer: PHP manager for IIS failed on server 2016, error 1603
Error message: “CustomAction VSDCA_VsdLaunchConditions returned actual error code 1603”
1. Install .net 3.5
2. Change this registry key:
to value 9 instead of 10
3. open Web Platform installer to reinstall php manager for iis this time it should work
4. set MajorVersion back to 10 again
When Azure AD Connect it configure to sync ad account to Azure AD/Office 365 it assigns the login name as the AD UPN (as expected), but it won’t assign that same UPN as the default email address – instead it assign a @mydomain.onmicrosoft.com as the primary email address.
to correct this we can use the Synchronization rules editor, which is installed together with the Azure AD Connect (Download Link)
In Synchronization rules editor, switch the direction tabs to outbound rules.
select the rule called “Out to ADD – UserExchangeOnline”, click edit and accept the option to disable and clone the rule (this will create a rule called ““Out to ADD – UserExchangeOnline – Cloned” that can be modified.
Change the precedence to 50
go to transformations, and Scroll down till you find the “Target Attribute” of “ProxyAddresses”
Change the FlowType to “Expressions” and enter the following in the source:
"SMTP:" & [userPrincipalName]
Now resync the users and the primary email address should be changed