Haha no, that's how it should look like. I set a fixed 1010 pixels and pushed it far to the left side. Bear in mind, only techtalk.cc is that way. I haven't touched foolsdesign.org... yet.
We don't have it in the middle now because we need some space on the right to show news and such (later in future) so the centered thing was not too good.
It will be fixed 1010 pixels for all screens.
We don't have it in the middle now because we need some space on the right to show news and such (later in future) so the centered thing was not too good.
It will be fixed 1010 pixels for all screens.
- techtalk.cc
- Posts: 1400
- Joined: 2014-02-27 07:51
- Contact:
Database went into recovery mode and the Web site "techtalk.cc" couldn't be reached.
The issue has now been fixed.
The issue has now been fixed.
- techtalk.cc
- Posts: 1400
- Joined: 2014-02-27 07:51
- Contact:
We just had a server downtime for a few minutes. An error in the backup forced a hard power off and restart of the server.
Again with this error message. It wasn't my fault it seems but this puts our techtalk.cc database into "recovery mode" so in case you see some odd connection error, this is what has happened.
Worry not, I'm trying to fix it. The database is just fine, however. This has something to do with the server, I might have chosen to allocate too little CPU resources to the server. I'll keep an eye on this.
Worry not, I'm trying to fix it. The database is just fine, however. This has something to do with the server, I might have chosen to allocate too little CPU resources to the server. I'll keep an eye on this.
aaaaaaaaaaaaaaargh! Got the error again! "#¤@£$@£!"#¤!"#¤@$£
"FCB::Open failed: Could not open file C:***.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.)."
It seems that you get the error only sometimes because our database files (MDF/LDF) are not located in their default locations in the "C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATA".
Probably some odd permission issue so I have now added the "NT ServiceMSSQLSERVER" (If you have a named instance: NT ServiceMSSQL$InstanceName) account to the files and folders of our MDF/LDF locations. (Full control)
Hopefully, it will solve this problem.
"FCB::Open failed: Could not open file C:***.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.)."
It seems that you get the error only sometimes because our database files (MDF/LDF) are not located in their default locations in the "C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATA".
Probably some odd permission issue so I have now added the "NT ServiceMSSQLSERVER" (If you have a named instance: NT ServiceMSSQL$InstanceName) account to the files and folders of our MDF/LDF locations. (Full control)
Hopefully, it will solve this problem.