error – FBA just stopped working – SharePoint 2019 – where to start troubleshooting

Hello All ~ i recently inherited a SP farm, it uses HNSC on top of one webApp, so no Central Admin GUI / web-interface 🙁

FBA has been working for months, then ~2 weeks ago, users get message ”
The server could not sign you in. Make sure your user name and password are correct, and then try again.” EVEN when their user/pass IS correct.

there are 2 app servers, 2 NLB web front end servers, 2 NLB OOS servers, 2 dist cache and 2 search servers.

i believe the visigo FBA pack solution has been installed, but this really doesn’t matter as everything was perfect for many months until just 2 wks ago.

FBA does have a dedicated SQL DB on our SQL always on avail. group (instance)

i don’t see a dedicated FBA website or application pool.
the role provider and connection string are defined (local) on both web front end servers at the server level

i have rebooted both app servers & both WFE servers but nothing changed.
i used the ULS viewer on the WFE servers to view logs at : C:Program FilesCommon Filesmicrosoft sharedWeb Server Extensions16LOGS

BUT saw NO events logged WHILE i was trying to login with an FBA account.
by the way everything else around FBA works (creating new users, etc…)

again this environment is new to me, and i’m more used to working in the CA web interface rather than strictly powershell

ANY IDEAS where i should begin to troubleshoot



troubleshooting – Why is my Nikon D3300 taking almost totally black pictures through the viewfinder but is fine on liveview?

Looks like the mirror may not be swinging out of the way correctly when the shutter fires. Try this :

Put the camera on viewfinder mode, put it to your eye and take a picture. The viewfinder image should go dark for a fraction of a second as the mirror swings out of the way and returns.

If it does, there could still be an issue with the synchronisation between the mirror and the shutter. Try a really long shutter time, say 1 second. If the mirror swing is just slightly delayed, you’ll probably get an image this time as the mirror gets out of the way part way through the exposure. If it’s gone really bonkers, the mirror might not move until the shutter closes, in which case the viewfinder won’t go dark until after the exposure is complete.

troubleshooting – What is the difference between flash control and flash compensation?

In the Nikon D5600 , there is the usual flash compensation setting where you can set it from -3.0 to +1.0
But there is also a setting called flash control in the menu , where you can set the flash to 1/32, 1/16 … all the way upto full.

Do both of these achieve the same thing, or is there any difference between these 2 ?

I tried both on the same composition . For flash compensation, image was brighter as it changed it from -3 to 1.
And for flash control also image was brighter as i changed it from 1/32 to FULL.
So, is there any difference between the two. ?

troubleshooting – Why does my Canon dSLR screen go black after taking two photos?

You “fix” it by taking the battery out and putting it back in. 😜

Seriously, it does sound like a bug in your camera, but it could be caused by a faulty battery or resolved by changing settings related to how long the screen stays on after taking a shot. Or could it be that your camera starts sending the screen output to a connected device (a phone or tablet, via wifi?)

What you describe, going off after taking two shots, and requiring removing and re-inserting the battery (not just turning on and off the power), sounds like a real issue, not just a default being reset by removing and re-inserting the battery. So there are a few possible fixes:

  1. You “fix” the problem by returning the camera to Canon (for in-warranty repairs).


  1. You “fix” the problem by installing a firmware update in your camera (possible fix, but I’m not sure)


  1. You experiment and see if any changes to possibly relevant settings fix the issue or change it (e.g. the display settings and/or pairing with a smartphone)


  1. You just shoot and ignore that screen on the back of your camera.

troubleshooting – Camera Broken? All Images White…camera takes pictures but when I view them it it just a white screen

The NX3300 is a mirrorless camera, so there is a bit less potential for confusion than with a DSLR. A DSLR tends to have a depth-of-focus preview mode that closes down the aperture to the value that is going to be used in the photograph. A DSLR, however, does not reflect the chosen ISO value or the shutter speed in what you get to see in the viewfinder.

A mirrorless camera reflects those in “preview” mode while it does not do so in “framing” mode. How those options are accessible with buttons or in menus differs between cameras and I am currently too lazy to search the online manuals for the information corresponding to the NX3300.

“framing” mode picks viewfinder exposure values (ISO and exposure time) that make it possible for you to see what you are pointing your camera at. It doesn’t guarantee that the picture will look anything like that.

In particular, it will not reflect over- or underexposure. I think that may be what is happening here to you: you are overexposing, for whatever reasons. Are you using “manual” mode or external flash?

OBS Studio troubleshooting

If you can do OBS Studio troubleshooting for blank capture screen then contact me. I already tried methods mentioned on Google Search Engine and did Windows 7 compability mode for OBS Studio, Run as Admin and Power Saving for AMD Graphics card.

If you can troubleshoot further and make OBS capture the game then contact me.

troubleshooting – Why won’t my Canon 400D/XTi turn on/off properly?

My camera is a Canon 400D (digital rebel XTi). It sat on a shelf for quite some time.

When I insert a (newly charged) battery, the camera doesn’t switch on. I get this screen:

back of camera, showing settings/controls

and switching the camera on/off doesn’t do anything. Without a lens mounted, I get this screen, and I can’t turn off the camera; I have to remove the battery to turn the camera off.

Before this problem appeared I replaced the clock battery with a new one, but I’m not sure that it caused this problem.

virtualization – Troubleshooting KVM’s guest anaconda installer logs

I am trying to install RHEL7.9 KVM guest on Ubuntu 18.04 Azure VM. The anaconda installer fails due to some error but the virt-viewer screen got closed so fast, I was unable to read what is the exact error. I know all anaconda logs get stored in /tmp/anaconda.log file on the KVM guest disk image but I am unable to figure out a way to check the contents of the file.
I tried mounting the KVM guest disk image using “mount -o loop .img ” command but it fails with NTFS signature is missing, thats probably because the installation fails before the KVM guest’s disk is partitioned properly.
I am looking for ways to check the contents of that file. Is there any way to redirect the anaconda logs of the guest machine to the Ubuntu host machine ?
Pasting the virt-install script and kickstart file used. The RHEL7.9 installation media was downloaded from site.

             --disk /datadrive/rhel79-oracle-$1.img,size=40,format=raw 
             --os-variant rhel7.0 
             --initrd-inject ./ks-rhel79-oracle.cfg 
             --vcpus 2 
             --memory 2048 
             --name rhel79-oracle-$1


# System authorization information
auth --passalgo=sha512 --useshadow

firstboot --disable
# Keyboard layouts
keyboard --vckeymap=us --xlayouts='us'
# System language
lang en_US.UTF-8
# Installation logging level
logging --level=debug
# Network information
network  --bootproto=dhcp --device=link --activate
network  --bootproto=dhcp --hostname=Azure-image
# Shutdown after installation
# Root password
rootpw --plaintext password
# SELinux configuration
selinux --disabled
# System services
services --enabled="sshd,chronyd"
# Do not configure the X Window System
# System timezone
timezone US/Eastern
# System bootloader configuration
bootloader --append="rootdelay=60 mpath crashkernel=2048M intel_idle.max_cstate=1 processor.max_cstate=1 transparent_hugepage=never numa_balancing=disable mce=ignore_ce modprobe.blacklist=kvm_intel,kvm,iTCO_wdt,iTCO_vendor_support,sb_edac,edac_core" --location=mbr
# Partition scheme
clearpart --all
# Disk partitioning information
part swap --fstype="swap" --size=32768
part / --fstype="xfs" --grow --size=6144

%post --logfile=/root/anaconda-composer.log --erroronfail
# Remove random-seed
rm /var/lib/systemd/random-seed

# Clear /etc/machine-id
rm /etc/machine-id
touch /etc/machine-id


%addon com_redhat_kdump --enable --reserve-mb=2048


sql server – Troubleshooting error message Invalid Object Name accessing MS SQL with python

Using python, I can connect to a MS SQL database, but cannot run any queries at all. I always get the error – invalid object name.

I understand from other stack exchanges that I may be accessing the wrong database (although that is specified in my connection); there may be something wrong in my schema (whatever that is); or I simply don’t have permission to run a query (I should have been given read only permissions).

My connection looks like:

import pyodbc

connSurvNet = pyodbc.connect(r'DRIVER={ODBC Driver 17 for SQL Server};' +
   ('SERVER={server},{port};' +
   # 'DATABASE={database};' +
   'UID={username};' +
   server= 'xxx',
   port= 1433,
   database= 'db',
   username= 'xxxx',
   password= 'xxxx')

In another database, I can download a table into a pandas dataframe with the following code:

df = pd.read_sql_query('''SELECT * FROM MyTable''', conn)

But from the database in question, MyTable is never a valid object name.

We have a gui interface for querying the data, which allows me to see the SQL-code used for the queries. It includes code like:

FROM (Data).(Version)

I’ve a pdf of the tables, with all the table names and columns, but nothing I enter as MyTable is ever valid.

I’ve run a few ideas from Stack Exchanges, like DB_SELECT(), which shows I’m connected to a database ‘master’, but I do not know of other things I can do to isolate my issue. Any further steps to understand my issue would be appreciated.

amazon web services – Troubleshooting block device mappings with Packer to increase size of EBS volume

I’d like to understand more about what to do when you need to increase a block device size for a build. I have some examples that work successfully with ubuntu 18, and centos 7 that I use, but it seems like each time I’m in a slightly new scenario the old techniques don’t apply, and that is probably due to a gap in my knowledge of what is required.

Building an AMI with NICE DCV (remote display):

name: DCV-AmazonLinux2-2020-2-9662-NVIDIA-450-89-x86_64

I tried this in my packer template:

  launch_block_device_mappings {
    device_name           = "/dev/sda1"
    volume_size           = 16
    volume_type           = "gp2"
    delete_on_termination = true

But then ssh never became available. I reverted to not doing any customisation, and took a look at the mounts:

(ec2-user@ip-172-31-39-29 ~)$ df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        482M     0  482M   0% /dev
tmpfs           492M     0  492M   0% /dev/shm
tmpfs           492M  740K  491M   1% /run
tmpfs           492M     0  492M   0% /sys/fs/cgroup
/dev/xvda1      8.0G  4.4G  3.7G  55% /
tmpfs            99M  8.0K   99M   1% /run/user/42
tmpfs            99M     0   99M   0% /run/user/1000

So I thought I should try this instead (which didn’t work):

  launch_block_device_mappings {
    device_name           = "/dev/xvda1"
    volume_size           = 20
    volume_type           = "gp2"
    delete_on_termination = true

which resulted in these errors:

==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: Authorizing access to port 22 from ( in the temporary security groups...
==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: Launching a source AWS instance...
==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: Adding tags to source instance
    amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: Adding tag: "Name": "Packer Builder"
==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: Error launching source instance: InvalidBlockDeviceMapping: Invalid device name /dev/xvda1
==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami:         status code: 400, request id: 2c419989-dd53-48ef-bcb6-6e54e892d152
==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: No volumes to clean up, skipping
==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: Deleting temporary security group...
==> amazon-ebs.amazonlinux2-nicedcv-nvidia-ami: Deleting temporary keypair...
Build 'amazon-ebs.amazonlinux2-nicedcv-nvidia-ami' errored after 1 second 820 milliseconds: Error launching source instance: InvalidBlockDeviceMapping: Invalid device name /dev/xvda1
        status code: 400, request id: 2c419989-dd53-48ef-bcb6-6e54e892d152

Would anyone be able to share some pointers on what I’d need to do to increase the volume size in this instance and why?