Содержание
- MSSQLSERVER_208
- Сведения
- Объяснение
- Возможные причины
- Действие пользователя
- MSSQLSERVER_208
- Details
- Explanation
- Possible Causes
- User Action
- How to Deal with Database Context Error 208 in SQL Server
- What is Error 208 in SSMS
- How to Solve Error 208 in SSMS
- MBO fetch operation failed in the mboset with the SQL error code 208
- Troubleshooting
- Problem
- Symptom
- Resolving The Problem
MSSQLSERVER_208
Применимо к: SQL Server (все поддерживаемые версии)
Сведения
| attribute | Значение |
|---|---|
| Название продукта | SQL Server |
| Идентификатор события | 208 |
| Источник события | MSSQLSERVER |
| Компонент | SQLEngine |
| Символическое имя | SQ_BADOBJECT |
| Текст сообщения | Недопустимое имя объекта «%.*ls». |
Объяснение
Не удается найти указанный объект.
Возможные причины
Возможны следующие причины возникновения этой ошибки.
Объект указан неверно.
Объект не существует в текущей базе данных или в указанной базе данных.
Объект существует, но пользователю не может быть предоставлен к нему доступ. Например, может оказаться так, что пользователь не имеет разрешений для доступа к объекту или объект создан в инструкции EXECUTE, но доступ к нему осуществляется вне области действия инструкции EXECUTE.
Действие пользователя
Проверьте следующую информацию и исправьте инструкцию соответствующим образом.
Имя объекта записано правильно.
Контекст текущей базы данных является правильным. Если не указано имя базы данных для объекта, то объект должен существовать в текущей базе данных. Дополнительные сведения о настройке контекста базы данных см. в разделе USE (Transact-SQL).
Объект существует в системных таблицах. Чтобы проверить существование таблицы или другого объекта на уровне схемы, отправьте запрос к представлению каталога sys.objects. Если объект отсутствует в системных таблицах, значит он был удален или у пользователя отсутствуют разрешения на просмотр метаданных объекта. Дополнительные сведения о разрешениях на просмотр метаданных объекта см. в статье Настройка видимости метаданных.
Объект содержится в применяемой по умолчанию схеме пользователя. Если его там нет, имя объекта нужно указывать в двухкомпонентном формате: имя_схемы.имя_объекта. Следует отметить, что скалярные функции должны всегда вызываться с использованием по меньшей мере двухкомпонентного имени.
Учет регистра в параметрах сортировки базы данных.
Если в базе данных используются параметры сортировки с учетом регистра, то имя объекта должно согласовываться по регистру с именем объекта в базе данных. Например, если определенный объект имеет имя MyTable в базе данных с параметрами сортировки с учетом регистра, запросы, в которых этот объект именуется как mytable или Mytable, будут возвращать ошибку 208, так как имена объектов не согласуются.
Параметры сортировки базы данных можно проверить, введя следующую инструкцию.
Аббревиатура CS в имени параметров сортировки указывает, что учитывается регистр символов. Например, значение Latin1_General_CS_AS определяет параметры сортировки с учетом регистра и с учетом диакритических знаков. Значение CI указывает, что в параметрах сортировки не учитывается регистр.
Пользователь имеет разрешение на получение доступа к объекту. Чтобы проверить, какие разрешения имеет пользователь для доступа к объекту, можно воспользоваться системной функцией Has_Perms_By_Name.
Источник
MSSQLSERVER_208
Applies to: SQL Server (all supported versions)
Details
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 208 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | SQ_BADOBJECT |
| Message Text | Invalid object name ‘%.*ls’. |
Explanation
The specified object cannot be found.
Possible Causes
This error can be caused by one of the following problems:
The object is not specified correctly.
The object does not exist in the current database or in the specified database.
The object exists, but could not be exposed to the user. For example, the user might not have permissions on the object or the object is created within an EXECUTE statement but accessed outside the scope of the EXECUTE statement.
User Action
Verify the following information and correct the statement as appropriate.
The object name is spelled correctly.
The current database context is correct. If a database name for the object is not specified, the object must exist in the current database. For more information about setting the database context, see USE (Transact-SQL).
The object exists in the system tables. To verify whether a table or other schema-scoped object exists, query the sys.objects catalog view. If the object is not in the system tables, the object has been deleted, or the user does not have permissions to view the object metadata. For more information about permissions to view object metadata, see Metadata Visibility Configuration.
The object is contained in the default schema of the user. If it is not, the object must be specified using the two-part format schema_name.object_name. Note that scalar-valued functions must always be invoked by using at least a two-part name.
The case sensitivity of the database collation.
When a database uses a case-sensitive collation, the object name must match the case of the object in the database. For example, when an object is specified as MyTable in a database with a case sensitive collation, queries that refer to the object as mytable or Mytable will cause error 208 to return because the object names do not match.
You can verify the database collation by running the following statement.
The abbreviation CS in the collation name indicates the collation is case sensitive. For example, Latin1_General_CS_AS is a case sensitive, accent sensitive collation. CI indicates a case insensitive collation.
The user has permission to access the object. To verify the permissions the user has on the object, use the Has_Perms_By_Name system function.
Источник
How to Deal with Database Context Error 208 in SQL Server
In this article we explain about ERROR 208, why it occurs and how to deal with it.
We often come across situations which seem to be very complicated and challenging but are actually very easy to get out of; provided we think logically. One such situation a lot of SQL Server DBA’s come across is the SSMS error 208, i.e. the ‘Invalid Object Name’ error. This is a very commonly occurring error which ends up confusing a lot of DBAs. So today, we will not only provide you with a solution to this problem, but also suggest you ways to avoid it from occurring in future.
What is Error 208 in SSMS
A lot of us or those DBAs who are not very experienced with using SQL Server, usually opt for exploring the software with the help of SQL Server Management Studio (SSMS). And while you are at it, you might click at a given object to know more about it, and suddenly come across a pop up stating ERROR 208! This is a point where a lot of you might get stuck. But after reading this article we hope things would get better as you would get a greater understanding of the subject.
What is most perplexing about this error to majority of DBAs is the fact that the object is visible to them in SSMS Object Explorer window but when they attempt to select it using T- SQL, they witness the error. This is the point where a lot of DBAs switch to extreme and desperate measures like restarting SSMS multiple times to furiously refreshing queries, restarting databases, etc. But to their sorrow, none of this will provide them with the solution they are looking for.
These practices fail to work because none of these is addressing the root cause of the error which is nothing but simple mismatch in database context.
How to Solve Error 208 in SSMS
Now that you know what is causing the error, finding the solution should not take long. The most common reason for this context mismatching error to occur is the fact that the default database context has been set to master. Well in 99 out of 100 cases, this ends up being the cause. And if this really is what is causing the error to appear in your system, then a very basic thing for you to do is changing the context of the database. And while you are at it, change it in a way that the context becomes similar to the current database object that is in use.
Once you perform this step, you will be glad to see that the error will appear no longer, and all other functions will also happen smoothly. This is one of those errors that almost every single DBA would have experienced, but few would actually know a way out of this situation without considering a repair sql action. This article would hopefully be of help to all of them. Apart from the solution given above, there is one more option that DBAs can try out; this involves prefixing multipart database name to the database that is in use. Or you might also want to change the database that opens by default once you login SSMS.
Источник
MBO fetch operation failed in the mboset with the SQL error code 208
Troubleshooting
Problem
Error BMXAA6713E. Record could not be retrieved from the database.
Symptom
The error above can happen on a Maximo 7.x running on SQL Server and the SQL error 208 happens when you try simple actions like filter by application object description in Security Groups app.
Security Groups —> Everyone —> Applications —> Filter the applications and type in WORKORDER in the MAIN Object box and hit enter. You get the following error:
BMXAA6713E — The MBO fetch operation failed in the mboset with the SQL error code 208. The record could not be retrieved from the database.
See the log file for more details about the error. More information.
In the logs you may see something like this :
[ERROR] [MAXIMO] [CID-UIASYNC-36] BMXAA6714E — The data for the next record in the mboset could not be retrieved for the SQL query select * from maxapps where (exists (select 1 from maximo.maxobject where ((upper (description) like ‘%WORKORDER%’)) and (objectname = maxapps.maintbname))) and (1=1) and (app in (‘CONDCODE’,’DRAWINDEX’,’ACTIVITY’,’TZRULE’,’SETS’,’PMOOB’,’SRVCOMMOD’,’SCHSUPER’,’MASTERPM’,’INTSRV’,’DM’,’TAGLOCKS’,’WOTRACKOOB’,’INTOBJECT’,’
TOOL’,’TECHPHONE’,’SROOB’,’QUICKREPOO’,’SCCONFIG’,’ACTION’,’BBOARD’,’FACONFIG’,’COMPANY’,’LAUNCH’,’TKTEMPLATE’,’OSLCRES’,’AMCREW’,’TERMCOND’,’FO
RGOTPSWD’,’CUSTAPP’,’INVUSAGE’,’MFMAILCFG’,’VIEWDRFT’,’RLADMIN’,’ASSETCAT’,’POOOB’,’INTERROR’,’WFADMIN’,’RFQ’,’REPLISTCFG’,’CONTPURCH’,’ASSET’,’LABOROOB’,’INVENTOR’,’VIEWSR’,’ROLE’,’RECEIPTS’,’CONTMASTER’,’INBXCONFIG’,’PRECAUTN’,’MOBDATAMAN’,’SCVNDIFACE’,’HAZARDS’,’CREATESROO’,’KPIGCONFIG’,’VIEWDR’,’DEPLCOLLS’,’INTMSGTRK’,’INVOICE’,’INVISSUEOO’,’WORKVIEW’,’ESCALATION’,’AMCREWT’,’DESIGNER’,’WOTRACK’,’KPITPL’,’IPC’,’AUTOSCRIPT’,’SCGLTIFACE’,’ITEMOOB’,’KPILCONFIG’,’SOLUTION’,’WSREGISTRY’,’SCTAXMAT’,’SCFMEA’,’SHIPREC’,’CIRCUITS’,’USER’,’PM’,’LOCATION’,’PO’,’PERSON’,’CURRENCY’,’METER’,’OSLCPROV’,’INVOKE’,’COMMTMPLT’,’RACEWAYS’,’CRAFT’,’SCVOIFACE’,’CREATEDROO’,’TOOLINV’,’JOBPLANOOB’,’REPORT’,’MPMAN’,’PLUSCTMPLT’,’MOBILEINV’,’SLA’,’COGNOSHOME’,’DOMAINADM’,’STOREROOM’,’RECEIPTSOO’,’COMPANI
ESO’,’IM’,’RPTOUTPUT’,’STARTCNTR’,’CHRTACCT’,’QUAL’,’KPIVIEWER’,’FAILURE’,’VIEWSROOB’,’SECUGRPMOB’,’INVISSUE’,’EXCHANGE’,’EMAILSTNER’,’CREATEINT’,’ECOMMADAPT’,’COLLECTION’,’PR’,’INVOICEOOB’,’SEARCHSOL’,’JOBPLAN’,’CRONTASK’,’SRVAD’,’RSCONFIG’,’PERSONGR’,’CONTLABOR’,’CONTLEASE’,’LOCATI_OOB’,’WORKMAN’,’VIEWTMPL’,’QUICKREP’,’MOBILEINST’,’ENDPOINT’,’FMEA’,’ITEM’,’TECHTABLET’,’TECHLITE’,’SAFEPLAN’,’RELATION’,’SELFREG’,’LOGGING’,’SRVITEM’,’MOBERRHND’,’LABOR’,’ASSETOOB’,’CONTWARRTY’,’LMO’,’PROPMAINT’,’ACTIONSCFG’,’EXTSYSTEM’,’SECURGROUP’,’ROUTES’,’INVENTOROO’,’KPI’,’METERGRP’,’FINCNTRL’,’RFQOOB’,’SR’,’CHANGEPSWD’,’DEPLGROUPS’,’CONDEXPMGR’,’CREATEDR’,’CREATESR’,’MULTISITE’,’COMPMASTER’,’CALENDR’,’COND’,’CONFIGUR’,’WFDESIGN’,’LABREP’,’PUBLISH’,’CITYPE’,’MANAGEINT’)) order by description OPTION (FAST 1000) . See the log file for more details about the error.
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name ‘maximo.maxobject’.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteCursored(SQLServerStatement.java:1879)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:766)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:616)
at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3186)
at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2798)
at psdi.mbo.MboSet.fetchMbos(MboSet.java:2755)
at psdi.mbo.MboSet.getMbo(MboSet.java:2002)
If you run the faulty query into SQL without the ‘maximo.’ before the object name in the SQL Server tool, it works perfectly
Resolving The Problem
This could be related with database ownership or a mismatch between the mxe.db.schemaowner / mxe.db.user in the System Properties app and the same info the maximo.properties file.
For example, in your System Properties app in Maximo, you have the following configuration :
mxe.db.schemaowner = dbo
mxe.db.user = maximo
However, in your maximo.properties file, your schema owner is not set to dbo, as in the property below :
As a solution for this, take these actions :
Источник
The error above can happen on a Maximo 7.x running on SQL Server and the SQL error 208 happens when you try simple actions like filter by application object description in Security Groups app.
Security Groups —> Everyone —> Applications —> Filter the applications and type in WORKORDER in the MAIN Object box and hit enter. You get the following error:
BMXAA6713E — The MBO fetch operation failed in the mboset with the SQL error code 208. The record could not be retrieved from the database.
See the log file for more details about the error. More information.
In the logs you may see something like this :
[ERROR] [MAXIMO] [CID-UIASYNC-36] BMXAA6714E — The data for the next record in the mboset could not be retrieved for the SQL query select * from maxapps where (exists (select 1 from maximo.maxobject where ((upper (description) like ‘%WORKORDER%’)) and (objectname = maxapps.maintbname))) and (1=1) and (app in (‘CONDCODE’,’DRAWINDEX’,’ACTIVITY’,’TZRULE’,’SETS’,’PMOOB’,’SRVCOMMOD’,’SCHSUPER’,’MASTERPM’,’INTSRV’,’DM’,’TAGLOCKS’,’WOTRACKOOB’,’INTOBJECT’,’
TOOL’,’TECHPHONE’,’SROOB’,’QUICKREPOO’,’SCCONFIG’,’ACTION’,’BBOARD’,’FACONFIG’,’COMPANY’,’LAUNCH’,’TKTEMPLATE’,’OSLCRES’,’AMCREW’,’TERMCOND’,’FO
RGOTPSWD’,’CUSTAPP’,’INVUSAGE’,’MFMAILCFG’,’VIEWDRFT’,’RLADMIN’,’ASSETCAT’,’POOOB’,’INTERROR’,’WFADMIN’,’RFQ’,’REPLISTCFG’,’CONTPURCH’,’ASSET’,’LABOROOB’,’INVENTOR’,’VIEWSR’,’ROLE’,’RECEIPTS’,’CONTMASTER’,’INBXCONFIG’,’PRECAUTN’,’MOBDATAMAN’,’SCVNDIFACE’,’HAZARDS’,’CREATESROO’,’KPIGCONFIG’,’VIEWDR’,’DEPLCOLLS’,’INTMSGTRK’,’INVOICE’,’INVISSUEOO’,’WORKVIEW’,’ESCALATION’,’AMCREWT’,’DESIGNER’,’WOTRACK’,’KPITPL’,’IPC’,’AUTOSCRIPT’,’SCGLTIFACE’,’ITEMOOB’,’KPILCONFIG’,’SOLUTION’,’WSREGISTRY’,’SCTAXMAT’,’SCFMEA’,’SHIPREC’,’CIRCUITS’,’USER’,’PM’,’LOCATION’,’PO’,’PERSON’,’CURRENCY’,’METER’,’OSLCPROV’,’INVOKE’,’COMMTMPLT’,’RACEWAYS’,’CRAFT’,’SCVOIFACE’,’CREATEDROO’,’TOOLINV’,’JOBPLANOOB’,’REPORT’,’MPMAN’,’PLUSCTMPLT’,’MOBILEINV’,’SLA’,’COGNOSHOME’,’DOMAINADM’,’STOREROOM’,’RECEIPTSOO’,’COMPANI
ESO’,’IM’,’RPTOUTPUT’,’STARTCNTR’,’CHRTACCT’,’QUAL’,’KPIVIEWER’,’FAILURE’,’VIEWSROOB’,’SECUGRPMOB’,’INVISSUE’,’EXCHANGE’,’EMAILSTNER’,’CREATEINT’,’ECOMMADAPT’,’COLLECTION’,’PR’,’INVOICEOOB’,’SEARCHSOL’,’JOBPLAN’,’CRONTASK’,’SRVAD’,’RSCONFIG’,’PERSONGR’,’CONTLABOR’,’CONTLEASE’,’LOCATI_OOB’,’WORKMAN’,’VIEWTMPL’,’QUICKREP’,’MOBILEINST’,’ENDPOINT’,’FMEA’,’ITEM’,’TECHTABLET’,’TECHLITE’,’SAFEPLAN’,’RELATION’,’SELFREG’,’LOGGING’,’SRVITEM’,’MOBERRHND’,’LABOR’,’ASSETOOB’,’CONTWARRTY’,’LMO’,’PROPMAINT’,’ACTIONSCFG’,’EXTSYSTEM’,’SECURGROUP’,’ROUTES’,’INVENTOROO’,’KPI’,’METERGRP’,’FINCNTRL’,’RFQOOB’,’SR’,’CHANGEPSWD’,’DEPLGROUPS’,’CONDEXPMGR’,’CREATEDR’,’CREATESR’,’MULTISITE’,’COMPMASTER’,’CALENDR’,’COND’,’CONFIGUR’,’WFDESIGN’,’LABREP’,’PUBLISH’,’CITYPE’,’MANAGEINT’)) order by description OPTION (FAST 1000) . See the log file for more details about the error.
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name ‘maximo.maxobject’.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteCursored(SQLServerStatement.java:1879)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:766)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:616)
at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3186)
at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2798)
at psdi.mbo.MboSet.fetchMbos(MboSet.java:2755)
at psdi.mbo.MboSet.getMbo(MboSet.java:2002)
If you run the faulty query into SQL without the ‘maximo.’ before the object name in the SQL Server tool, it works perfectly
Click here follow the steps to fix Microsoft Sql Server Error Code 208 and related errors.
|
|
|
|
To Fix (Microsoft Sql Server Error Code 208) error you need to |
|
|
Step 1: |
|
|---|---|
| Download (Microsoft Sql Server Error Code 208) Repair Tool |
|
|
Step 2: |
|
| Click the «Scan» button | |
|
Step 3: |
|
| Click ‘Fix All‘ and you’re done! | |
|
Compatibility:
Limitations: |
Microsoft Sql Server Error Code 208 Error Codes are caused in one way or another by misconfigured system files
in your windows operating system.
If you have Microsoft Sql Server Error Code 208 errors then we strongly recommend that you
Download (Microsoft Sql Server Error Code 208) Repair Tool.
This article contains information that shows you how to fix
Microsoft Sql Server Error Code 208
both
(manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Microsoft Sql Server Error Code 208 error code that you may receive.
Note:
This article was updated on 2023-02-04 and previously published under WIKI_Q210794
Contents
- 1. What is Microsoft Sql Server Error Code 208 error?
- 2. What causes Microsoft Sql Server Error Code 208 error?
- 3. How to easily fix Microsoft Sql Server Error Code 208 errors
What is Microsoft Sql Server Error Code 208 error?
The Microsoft Sql Server Error Code 208 error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.
This code is used by the vendor to identify the error caused. This Microsoft Sql Server Error Code 208 error code has a numeric error number and a technical description. In some cases the error may have more parameters in Microsoft Sql Server Error Code 208 format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.
What causes Microsoft Sql Server Error Code 208 error?
The Microsoft Sql Server Error Code 208 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.
There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.
How to easily fix Microsoft Sql Server Error Code 208 error?
There are two (2) ways to fix Microsoft Sql Server Error Code 208 Error:
Advanced Computer User Solution (manual update):
1) Start your computer and log on as an administrator.
2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.
3) In the new window, select «Restore my computer to an earlier time» option and then click Next.
4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.
5) Click Next on the confirmation window.
6) Restarts the computer when the restoration is finished.
Novice Computer User Solution (completely automated):
1) Download (Microsoft Sql Server Error Code 208) repair utility.
2) Install program and click Scan button.
3) Click the Fix Errors button when scan is completed.
4) Restart your computer.
How does it work?
This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)