> # Changing the Service Connection Model

> When you use the ServiceConnectionModel attribute to change the connection model for a service, the SequeLink service sometimes reports multiple internal errors. When you examine the SequeLink packet log, you see the following messages:

>     Wed May 16 10:39:45 2007:Internal error, error detected in the event
>     processor.
>     Wed May 16 10:39:45 2007:SequeLink Common
>     Library.SWANDM_Entity_FindFirstKeyValue.3820().21.The specified attribute
>     does not exist.
>     Wed May 16 10:39:45 2007:SequeLink Common
>     Library.SWANDM_Entity_FindFirstKeyValue.3820().21.The specified attribute
>     does not exist.
>     ...
>     Wed May 16 10:39:45 2007:Internal error, error detected in the event
>     processor.
>     Wed May 16 10:39:45 2007:Internal error, error detected in the event
>     processor.
>     ...

> To avoid internal errors when changing the connection model, perform the following steps:

> 1. Make sure the services have the ServiceConnectionModel attribute set to the value you want.
> 2. Delete both the Monitoring profile and Event trace profile of the services that have changed.
> 3. Create new Monitoring and Event trace profiles.
> 4. Stop all SequeLink services.
> 5. Stop the Agent.
> 6. Restart the Agent.
> 7. Restart all SequeLink services.