You can get rid of /_layouts/15/start.aspx in the URL by going to Site Actions -> Site Settings -> Manager Site Features -> Deactivate Minimal Download Strategy feature

However this is a new framework in SharePoint 2013, which increases performance of SharePoint site..

More reading here:

What is /_layouts/15/start.aspx

Why does /_layouts/15/start.aspx appear as part of SharePoint 2013 URL

In the event logs, I found out, that I have errors in system logs:

• Event Id: 7031, 7034;
• source: Service Control Manager;
• details: The SharePoint 2010 User Code Host service terminated unexpectedly.

I found out, that service account that was running Sandbox code service needs to have access to performance counters on the server. So what you need to do is pretty simple, you need to grant service account access to counters and you can do it by adding service account as a member of local group Performace Monitor Users in Server Manger.

Thanks to https://sajiviswam.wordpress.com/2011/04/15/the-machine-default-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-000c101c-0000-0000-c000-000000000046-sharepoint-2010/

This error is being logged into the System event logs in Event Viewer due to inadequate permission for the farm admin account on the DCOM component 000C101C-0000-0000-C000-000000000046. In order to change the permission settings, perform the following steps.

1. Open Component Service by clicking Start > Administrative Tools > Component Services.
2. Navigate and expand the node Component Services > Computers > My Computer > DCOM Config.
3. Right Click the sub node “000C101C-0000-0000-C000-000000000046” and select “Properties”.
4. On the Properties dialog box, select Security tab. In most cases you will notice that the settings are grayed out. This is because the logged in user doesn’t have enough permissions on this component to change the settings. In order to provide this permissions, perform the steps described in next section “Change Component Service Owner and Permission”. You may need to restart the server after doing this.
5. Once you set up the permission mentioned in previous step, in the Launch and Activation Permissions section in Security tab, select Customize option and click Edit.
6. In the popup window, add the farm admin user account and check Local Launch and Local Activation permissions.
7. Restart IIS and SP Timer. If possible, restart the server itself.

Change Component Service Owner and Permission

In the DCOM Config dialog box, you noticed that the settings are grayed out. In order to enable those settings, perform the following registry modification.

1. Open Registry Editor by typing “regedit.exe” in Start > Run.
2. Navigate and select the key “[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{000C101C-0000-0000-C000-000000000046}]”
3. Right click and select Permissions.
4. In the popup windows, click Advanced.
5. In the Advanced Security Settings windows, select Owner tab and change the owner to Administrators. Click OK to close the window.
6. In the Permissions screen, select Administrators and check Full Control. Click OK to close the screen.
7. Close the registry editor.

• Site Quotas and Lock in Central Administration (option is greyed-out)
• Stsadm : operation completes successfully but no change
• Using PowerShell : same behavior as stsadm

From this guy: http://www.bleepingtech.com/windows-8-fix-this-app-cant-open-for-built-in-administrator-account/

You might have encountered with this strange and annoying error.  This app can’t open for Built-in Administrator account please sign in with a different account and try again. or  while User Account Control is turned off. You need to turn on UAC . There is an easy solution for the error.

Solution for Windows 8 App Error:
•Hold the  Windows key + R  and in run dialog box type: secpol.msc
•Go to Local Policies –> Security Options –> Scroll down and find “User Access Control: Admin Approval Mode For built in…..”
•Double click on it and select enabled and the press ok
•Again press windows key and R and type  regedit
•Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\UIPI
•On the right hand side double click on default and change the value to 0x00000001(1) and click ok
•Restart your computer and all the apps should work.

Source of Post: http://sqlite.awardspace.info/syntax/sqliteodbc.htm

Microsoft Access Forms and Queries can used as a front end for SQLite datebases by using the free ODBC driver written by Christian Werner which can be found at http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe.

What can be done.

1. Link to SQLite Databases and tables allowing you to add, update and delete the records in them.
2. Import SQLite tables into Access.
3. Create tables in SQLite Databases by exporting tables and query results from MS Access.

What can not be done.

1. Delete SQLite tables- you may only delete the link to the table
2. Alter the structure of a sqlite table within MS Access.

Set up the ODBC Data Source on Windows XP

1. Run the installation program sqliteodbc.exe
2. Go to the control panel and look for "Data Sources (ODBC)".
   It may have it's own icon in the control panel or it may be listed in Administrative Tools
3. Click on "Data Sources (ODBC)" which will bring up the "ODBC Data Source Administrator Dialog" Box.
4. In the &#User DSN" tab select Add to bring up the "Create New Datasource" dialog box.
5. Select the appropriate driver most likely the "SQLite 3 ODBC Driver".
6. Enter the data source name and your done.

Create Table in SQLite from MS ACCESS

Steps to create a table in SQLite from Microsoft Access.
From the menu bar in Access, go to;

1. File - Export
2. Export Table Dialog Box
3. "Save As Type" drop down box
4. Select "ODBC Databases"
5. Export to File Name
6. Select Machine Data Source Tab
7. Select "SQLite Database"
8. Click OK
9. SQLite 3 ODBC Driver Connect
10. Browse for database name

Linking to tables in a SQLite database from MS Access

1. Go to the File menu
2. Select "Get External Data"
3. Select "Link Tables"
4. Link dialog Box
5. Files of type drop down box
6. Select ODBC Databases()
7. Machine Data Source Tab
8. Select "SQLite Database"
9. Select "Sqlite 3 ODBC Driver Connect"
10. Database Name
11. Browse for file

PROBLEM:

Some users of an ACCDE file get this error message:

"The database cannot be opened because the VBA project contained in it cannot be read."

Here are the details of what I'm doing:

1. I Make ACCDE from MS Access 2010

2. I put ACCDE on the network

3. Users try to load the ACCDE.

4. Some users are successful.

5. Some users get this message:

"The database cannot be opened because the VBA project contained in it cannot be read."

All users have the same install procedure:

1. Project Referenced DLLs

2. MS Access 2010 Runtime

Notes:

1. The ACCDB file opens and runs properly in Access Development Environment.

2. The ACCDE worked at some point on the user's machine that it now not working.

3. Some of the previous versions now do not work either.

4. We have tried decompiling , compact and repair, and starting a new DB and copying the objects in.

SOLUTION:

You have compiled the MS Access application with a version that is higher than the one used by the person trying to open the ACCDE file.

This could be as simple as compiling with MS Office 14.0.7151.5001 and the users getting the error is running 14.0.4760.1000. Onece the user is updated to 14.0.7151.5001 then the applicatioin will work again.

https://support.microsoft.com/en-us/kb/2533794

In MS Access, sometimes you can get a Write Conflict when trying to update a table that is linked to SQL Server. Following is two suggestions on how to resolve the issue.

1. If the SQL Server table has a bit column, then set a default of 0 or 1 and then do not allow NULLS.

2. If the Table has a nvarchar(MAX) or very large field like nvarchar(4000) then try adding a column of datatype "timestamp".

http://aghy.hu/blog/missing-blank-site-template-in-sharepoint-2013 Thanks Aghy!

When setting up site collections, I mostly use the Blank Site Template. But in SharePoint 2013, there's a big "surprise": no Blank Site Template. Neither for Site Collections nor for subsites:

But hey, I need it back! I want it back! Don't you?

There are two tricks I found.

First, there's still possible to create blank sites by using PowerShell:

1. Run the command Get-SPWebTemplate to get the full list of the available templates. You can see, the Blank Site template is still there, and it's ID is STS#1:

   

2. From this point, creating a new site collection is as easy as this:

   $template = Get-SPWebTemplate "STS#1"

   New-SPSite -Url "<URL for the new site collection>" -OwnerAlias "<domain\user>" -Template $template

Second, believe or not, you can enable this site template for the UI too. Just go to the folder C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\1033\XML, and open the WEBTEMP.XML file. There, you'll find a line like this:

<Configuration ID="1" Title="Blank Site" Hidden="TRUE" ImageUrl="/_layouts/15/images/stbs.png?rev=23" Description="A blank site for you to customize based on your requirements." DisplayCategory="Collaboration" AllowGlobalFeatureAssociations="False" > </Configuration>

Here you go: just change the highlighted tag from Hidden="TRUE" to Hidden="FALSE", save the file, and that's it: next time you want to create a new site, you'll get the Blank Site Template:

NOTE: The term, "DSN-less connection" is not accurate when using Pervasive.SQL relational access, since a DSN must be defined on the server using the Pervasive ODBC Engine Interface.

In the Example below TDATA System DSN Must exist on the server.

If InStr(1, tblDef.Connect, "ODBC") > 0 Then
 'SQL Pervasive Database
 strSQLConnectionString = GetSQLConnectionString()
 'tblDef.Connect = strSQLConnectionString
 tblDef.Connect = "ODBC;driver={Pervasive ODBC Client Interface};ServerName=10.1.0.16;ServerDSN=TDATA;" & ";TABLE=" & tblDef.Name
 tblDef.RefreshLink
End If

More information is here

http://support.pervasive.com/t5/tkb/articleprintpage/tkb-id/Database_KnowledgeBase/article-id/804

Solution Notes

NOTE: The term, "DSN-less connection" is not accurate when using Pervasive.SQL relational access, since a DSN must be defined on the server using the Pervasive ODBC Engine Interface.

The following connection strings can be used to access Pervasive ODBC Engine DSNs programmatically:

1) Setup a DSN on the client machine using the Pervasive ODBC Client Interface. Connection String can be "DSN=myDSN;", assuming the client side DSN is named as myDSN.

2) Without setting up a DSN on the client machine:
Connection String can be "driver={Pervasive ODBC Client Interface};ServerName=myServer;ServerDSN=myDSN;" or
Connection String can be "driver={Pervasive ODBC Client Interface};ServerName=myServer;DBQ=dbName;"

NOTE: Here, myServer is the server name or IP address; myDSN is the server side DSN using the Pervasive ODBC Engine Interface; dbName is the database which is used to define the server side DSN